On Tue, Jan 22, 2013 at 5:13 PM, Kris Borchers <kris(a)redhat.com> wrote:
On Jan 22, 2013, at 10:11 AM, Summers Pittman <supittma(a)redhat.com> wrote:
> On 01/22/2013 11:08 AM, Matthias Wessendorf wrote:
>> On Tue, Jan 22, 2013 at 4:20 PM, Kris Borchers <kris(a)redhat.com> wrote:
>>> Not sure what you mean. Are you saying you aren't going to implement the
provider right now?
>> Yes, when the paging is at root level (-> twitter), we are good.
>>
>>> I think that is something that should be in 1.0, IMO.
>> Sure, if there is time, it can come in after M8?
>>
>>
>> -M
>>
> It may be enough to include in PipeConfig a "resultPath" String which is
> the dotted path to the JSON result. Then we just use the
> nextIdentified/previousIdentifier fields in the spec to get the rest.
I was also thinking that but technically, you can have a "." in your key name
if you put quotes around it so that makes it more difficult.
I think for now, on iOS, I am just supporting the case like twitter -
where the metadata is at root level...
If there is (user) demand for other solutions... I don't mind going
that route...
-M
> _______________________________________________
> 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