Should AGFilterConfig.
scrollingMetaDataLocation perhaps be a Pipe level
thing (like encoding or authentication) instead of a request level
thing? I don't imagine it changing during the lifetime of a Pipe?
Otherwise looks really good!
I also updated the "comparison" gist:
https://gist.github.com/4546737
Feedback welcome....
On Wed, Jan 16, 2013 at 4:28 PM, Sebastien Blanc <scm.blanc(a)gmail.com> wrote:
> the timeout parameter would be a general property of read() and not related
> to Paging ?
>
>
> On Wed, Jan 16, 2013 at 4:25 PM, Summers Pittman <supittma(a)redhat.com>
> wrote:
>> On 01/16/2013 10:23 AM, Bruno Oliveira wrote:
>>> Good point Summers. Might be an obvious question, but there we go. Are
>>> we planning to include timeout as parameter? For example: I want to retrieve
>>> a list of a bazilion users, and I want to specify the timeout acceptable to
>>> wait.
>>>
>>> I didn't get the chance to look at each API, just double checking here.
>>>
>> +1
>>
>> I was thinking about this yesterday. I want to but was hoping we could
>> get the "shape" of the API nailed down first before we started
hammering
>> on specifics.
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev(a)lists.jboss.org
>>
https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/aerogear-dev
>