kborchers/gist:4541757

## gistfile1.txt
[14:06:02] <+sblanc>41 kborchers: is your biggest concern that read({some filters_options}) will return a "decorated" object containing next(), prev() etc functions ?
[14:08:21] <@qmx>	 kborchers: I don't have any problems on diverging APIs
[14:08:40] <@qmx>	 kborchers: but the spirit should be the same, bourbon & whisky don't mix well
[14:08:46] <@qmx>	 :P
[14:09:00] qmx	 always wanted to use this sentence
[14:09:52] <+kborchers>	 sblanc: yes … basically. since a read is async, i am returning the deferred containing my callbacks which handle the different results of that deferred. i have no need to hang on to this but this change would require me to hang onto this and drag it around with me. then i effectively issue reads (next(), prev(), etc.) against that object instead of my pipe which seems wrong
[14:09:55] <+abstractj>	 qmx++
[14:09:56] <aerobot>	 qmx is on the rise! (Karma: 109)
[14:10:18] <+kborchers>	 qmx: i also don't mind diverging APIs when necessary
[14:10:21] <+kborchers>	 qmx: bourbon is whiskey :P
[14:10:51] <+abstractj>	 kborchers is like samba & rock to qmx. They are the same
[14:10:57] <+kborchers>	 LOLOLOL
[14:11:08] abstractj	 hides
[14:11:11] <+kborchers>	 heavy metal === samba, ok i get it
[14:12:07] <+sblanc>	 kborchers: okay but besides impl details, you say you prefer pipe.next() , isn't that also strange to call next() on a pipe ? (on design level)
[14:12:14] <+summersp>	 kborchers, in javascript when you are in the success callback, does "this" reference the callback method?
[14:12:35] <@qmx>	 sblanc: kborchers is wrong, let's go full steam on try to convince it that perl is good
[14:13:14] <+sblanc>	 qmx: let's follow this advises http://stackoverflow.com/questions/3707646/how-can-i-do-paging-and-sorting-in-a-perl-cgi-program
[14:13:30] <+abstractj>	 sblanc ZOMG
[14:13:43] <+kborchers>	 sblanc: that was only to be in line with the other proposals which had those methods … .next() would just be a "helper" for api alignment which would just call .read({page:"next"}); or something like that
	[14:06:02] <+sblanc>41 kborchers: is your biggest concern that read({some filters_options}) will return a "decorated" object containing next(), prev() etc functions ?
	[14:08:21] <@qmx> kborchers: I don't have any problems on diverging APIs
	[14:08:40] <@qmx> kborchers: but the spirit should be the same, bourbon & whisky don't mix well
	[14:08:46] <@qmx> :P
	[14:09:00] qmx always wanted to use this sentence
	[14:09:52] <+kborchers> sblanc: yes … basically. since a read is async, i am returning the deferred containing my callbacks which handle the different results of that deferred. i have no need to hang on to this but this change would require me to hang onto this and drag it around with me. then i effectively issue reads (next(), prev(), etc.) against that object instead of my pipe which seems wrong
	[14:09:55] <+abstractj> qmx++
	[14:09:56] <aerobot> qmx is on the rise! (Karma: 109)
	[14:10:18] <+kborchers> qmx: i also don't mind diverging APIs when necessary
	[14:10:21] <+kborchers> qmx: bourbon is whiskey :P
	[14:10:51] <+abstractj> kborchers is like samba & rock to qmx. They are the same
	[14:10:57] <+kborchers> LOLOLOL
	[14:11:08] abstractj hides
	[14:11:11] <+kborchers> heavy metal === samba, ok i get it
	[14:12:07] <+sblanc> kborchers: okay but besides impl details, you say you prefer pipe.next() , isn't that also strange to call next() on a pipe ? (on design level)
	[14:12:14] <+summersp> kborchers, in javascript when you are in the success callback, does "this" reference the callback method?
	[14:12:35] <@qmx> sblanc: kborchers is wrong, let's go full steam on try to convince it that perl is good
	[14:13:14] <+sblanc> qmx: let's follow this advises http://stackoverflow.com/questions/3707646/how-can-i-do-paging-and-sorting-in-a-perl-cgi-program
	[14:13:30] <+abstractj> sblanc ZOMG
	[14:13:43] <+kborchers> sblanc: that was only to be in line with the other proposals which had those methods … .next() would just be a "helper" for api alignment which would just call .read({page:"next"}); or something like that