On Fri, Nov 15, 2013 at 4:44 PM, Oswald Buddenhagen <[email protected]> wrote: > On Fri, Nov 15, 2013 at 02:35:44PM -0600, Felipe Contreras wrote: >> On Thu, Nov 14, 2013 at 4:49 PM, Oswald Buddenhagen <[email protected]> wrote: >> > On Thu, Nov 14, 2013 at 05:30:08AM -0600, Felipe Contreras wrote: >> >> On Tue, Nov 12, 2013 at 5:55 AM, Oswald Buddenhagen <[email protected]> wrote: >> >> > On Tue, Nov 12, 2013 at 05:06:08AM -0600, Felipe Contreras wrote: >> >> >> On Tue, Nov 12, 2013 at 4:40 AM, Oswald Buddenhagen <[email protected]> >> >> >> wrote:
>> >> >> > well, there are two considerations: >> >> >> > - i didn't want to change the default behavior >> >> >> > - i wanted to default to the safe (don't miss messages) option. >> >> >> > though >> >> >> > it can be argued that this default is unsafe as far as the size of >> >> >> > the >> >> >> > initial fetch goes. so maybe i should just make it error out if >> >> >> > MaxMessages is exceeded by more than 50% and no explicit setting is >> >> >> > present. >> >> >> >> >> >> That is orthogonal; the default of ExemptUnread can be 'yes'. >> >> >> >> >> > huh? >> >> >> >> ExceptUnread = yes doesn't change the default behavior.. >> >> >> > yes ... so what exactly does the orthogonality refer to? >> >> The default behavior is independent of the name of the variable. >> > correct. > too bad that you were replying to a selective quote which explicitly > excluded the topic of naming. You said this: >> >> >> > - i didn't want to change the default behavior That's a red herring. The default behavior wouldn't change either way. >> >> Besides, once you add the ExcessMessageMode: Keep option, it wouldn't >> >> really be "expiring" anything, would it? >> >> >> > it would still expire from the "working set". >> >> What does that even mean? >> >> http://www.merriam-webster.com/dictionary/expire >> >> : to end : to no longer be valid after a period of time >> >> : to die >> >> To die from the "working set"? To no longer be valid after a period of >> time from the "working set"? What the f*ck is that? >> > are you actually lacking the language background, or are you just being > contrarian for the sake of it? Neither, it doesn't make any sense. > i for one find the association quite natural, and clearly i'm not > alone with that - the term is fairly established in this context. Show me the evidence. Show me one instance where expire is used to refer to exclude something from a working set. >> And at no point in time are you even touching LimitUnread. >> > actually, i did. right in the previous message. No, you didn't. >> [...] you made your mind and you are simply defending what you already >> decided and no argument is going to change your mind. >> > or maybe your arguments just aren't that convincing. ;) If that was the case you wouldn't have any problem with a vote. -- Felipe Contreras ------------------------------------------------------------------------------ DreamFactory - Open Source REST & JSON Services for HTML5 & Native Apps OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access Free app hosting. Or install the open source package on any LAMP server. Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native! http://pubads.g.doubleclick.net/gampad/clk?id=63469471&iu=/4140/ostg.clktrk _______________________________________________ isync-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/isync-devel
