[3544] in BarnOwl Developers
Re: [barnowl] IRC reconnect (#108)
daemon@ATHENA.MIT.EDU (Jason Gross)
Thu Aug 8 16:10:20 2013
Date: Thu, 08 Aug 2013 13:09:33 -0700
From: Jason Gross <notifications@github.com>
Reply-To: barnowl/barnowl <reply+i-9709132-2001beb80c08e30b034e487c72b5d6a5a38438fb-4475081@reply.github.com>
To: barnowl/barnowl <barnowl@noreply.github.com>
In-Reply-To: <barnowl/barnowl/pull/108@github.com>
----==_mimepart_5203fafd12dae_3a566cfd54368b
Date: Thu, 08 Aug 2013 13:09:33 -0700
Mime-Version: 1.0
Content-Type: text/plain;
charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-ID: <5203fafd15180_3a566cfd543691f@worker3.rs.github.com.mail>
> I think the key difference is that .zephyr.subs always consults the file, whereas your current implementation will short-circuit checking the file under some circumstances.
I view both .zephyr.subs and ~/.owl/irchannels as for persisting subs across BarnOwl restarts. The purpose of the internal hash is, IMO, to persist subs across connection interrupts. AFS blips, which is the closest I can think of to an interrupted connection for zephyr, generally don't require re-subscribing. And the things which are serious enough to warrant `:loadsubs` `:loadloginsubs` still need to be dealt with manually.
Personally, I think the `-t` distinction being "local to this BarnOwl session" vs. "global across BarnOwl restarts" makes more sense than if it were "until the next time I lose IRC connectivity" vs. "forever".
---
Reply to this email directly or view it on GitHub:
https://github.com/barnowl/barnowl/pull/108#issuecomment-22351768
----==_mimepart_5203fafd12dae_3a566cfd54368b
Date: Thu, 08 Aug 2013 13:09:33 -0700
Mime-Version: 1.0
Content-Type: text/html;
charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-ID: <5203fafd15c75_3a566cfd543705a@worker3.rs.github.com.mail>
<blockquote>
<p>I think the key difference is that .zephyr.subs always consults the file, whereas your current implementation will short-circuit checking the file under some circumstances.</p>
</blockquote>
<p>I view both .zephyr.subs and ~/.owl/irchannels as for persisting subs across BarnOwl restarts. The purpose of the internal hash is, IMO, to persist subs across connection interrupts. AFS blips, which is the closest I can think of to an interrupted connection for zephyr, generally don't require re-subscribing. And the things which are serious enough to warrant <code>:loadsubs</code> <code>:loadloginsubs</code> still need to be dealt with manually.</p>
<p>Personally, I think the <code>-t</code> distinction being "local to this BarnOwl session" vs. "global across BarnOwl restarts" makes more sense than if it were "until the next time I lose IRC connectivity" vs. "forever".</p>
<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br>Reply to this email directly or <a href='https://github.com/barnowl/barnowl/pull/108#issuecomment-22351768'>view it on GitHub</a>.<img src='https://github.com/notifications/beacon/JJk3yKd0u6qAmPAmJXdf9_gRuUTQCipO-dP0x97pmbFICXxk9_eKsAFlYwLIF2Vi.gif' height='1' width='1'></p>
----==_mimepart_5203fafd12dae_3a566cfd54368b--
