Yuck, indexBy seems sorta gross. Does the php support this already?
Perhaps we can push this transform outside of the service into some helper
logic..
On Wed, Jun 18, 2008 at 4:08 PM, Chris Chabot <[EMAIL PROTECTED]> wrote:
> (not a response to the actual proposal, more of a general thing):
>
> Remember that the RESTful spec also mentioned having an indexBy, so that
> should be added (in whichever interface definition). An indexBy should have
> the following result (cut&paste from spec doc):
>
> {
> "entry" :
> [
> { "id" : "example.org:34KJDCSKJN2HHF0DW20394", "pokes" : 3,
> "last_poke" : "2008-02-13T18:30:02Z" },
> { "id" : "example.org:58UIDCSIOP233FDKK3HD44", "pokes" : 2,
> "last_poke" : "2007-12-16T18:30:02Z" }
> ]
> }
>
> application/json representation (with indexBy=id):
>
> {
> "entry" : {
> "example.org:34KJDCSKJN2HHF0DW20394" : {"pokes" : 3, "last_poke" :
> "2008-02-13T18:30:02Z" },
> "example.org:58UIDCSIOP233FDKK3HD44" : {"pokes" : 2, "last_poke" :
> "2007-12-16T18:30:02Z" }
>
> }
> }
>
> On Jun 19, 2008, at 12:57 AM, Cassie wrote:
>
> public ResponseItem<RestfulCollection<T>> getItems(UserId userId,
>> GroupId groupId, String appId, Set<String> fields, SortOrder sort,
>> SortDirection direction, FilterType filter,
>> int first, int max, SecurityToken token);
>>
>
>
