On Wed, Jan 23, 2013 at 2:46 PM, Kris Borchers <kris(a)redhat.com> wrote:
On Jan 23, 2013, at 7:42 AM, Matthias Wessendorf <matzew(a)apache.org> wrote:
> On Wed, Jan 23, 2013 at 2:12 PM, Kris Borchers <kris(a)redhat.com> wrote:
>>
>> On Jan 23, 2013, at 5:23 AM, Matthias Wessendorf <matzew(a)apache.org>
wrote:
>>
>>> Hi,
>>>
>>> reading the [spec]:
>>> ```
>>> pagingLocation: String, indicate whether paging information is sent as
>>> query parameters (default), or on the request header.
>>> ```
>>> 1)
>>> I think we need one more config setting, to say under what specific
>>> header the server is expecting the "query information".
>>>
>>> Like:
>>> httpRequest.addHeader("My-Awful-Query", someValue);
>>> // where the "My-Awful-Query" is replaced by the actual header key
>>
>> I haven't gotten this far but sounds like it would be an issue. What about,
dare I say, another provider? The reason I suggest this is what if they want each param in
a different header? I have honestly never seen information like this sent as headers so
it's all strange to me.
>
> Actually.... let's simply skip the header.... and just go with query......
>
> IF ... some bizzare server requires that _AND_ it we are asked to
> support taht, I am willing to put the support of that in.... but not
> now - to be honest
+1
see:
https://github.com/aerogear/aerogear.org/commit/562230d706649adb08d7fd34c...
>
>
>
>>
>>>
>>> 2)
>>> Name suggestions:
>>> -queryHeaderIdentifier
>>> -queryHeaderName
>>> -queryHeader
>>>
>>> 3)
>>> Perhaps a minor thing... but I think I don't like the
'pagingLocation'
>>> name... if you just read that name, it is NOT (for me) clear
>>> that this drives if the query strings is sent as a)header value or
>>> b)appended as http query.
>>
>> What about something like pagingTransport or parameterTransport or pagingVehicle
or something like that?
>>>
>>> Any thoughts?
>>>
>>> -Matthias
>>>
>>> [spec]
https://github.com/aerogear/aerogear.org/blob/client_paging_spec/docs/spe...
>>>
>>> --
>>> Matthias Wessendorf
>>>
>>> blog:
http://matthiaswessendorf.wordpress.com/
>>> sessions:
http://www.slideshare.net/mwessendorf
>>> twitter:
http://twitter.com/mwessendorf
>>> _______________________________________________
>>> 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
>
>
>
> --
> Matthias Wessendorf
>
> blog:
http://matthiaswessendorf.wordpress.com/
> sessions:
http://www.slideshare.net/mwessendorf
> twitter:
http://twitter.com/mwessendorf
>
> _______________________________________________
> 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
--
Matthias Wessendorf
blog:
http://matthiaswessendorf.wordpress.com/
sessions:
http://www.slideshare.net/mwessendorf
twitter:
http://twitter.com/mwessendorf