For JSON-RPC batches you should be able to return not-implemented for specific requests with the others going through. (Though I'd have to check how PHP handles this vs Java)
Also note that there are slightly different standards for portable contacts (aka people) requests. Those responses have filtered/sorted/updatedSince fields for this purpose. See: http://portablecontacts.net/draft-spec.html#declining On Thu, Jun 24, 2010 at 3:44 AM, Justin Wyllie <[email protected]>wrote: > > Hi > Let's say we basically implement the people service but we do not support > getting friends who have an app, The filterBy field of 'hasApp'. > In the case of a JSON-RPC call this might return a data structure with > results for some labels e.g. > "result":{"startIndex":0,"totalResults":1,"itemsPerPage":20,"list":[{"id":"john.doe","isOwner":true,"isViewer":false,"name":{"familyName":"Doe","givenName":"John","formatted":"John > Doe"},"displayName":"Johnny"} > but for the label hasAppViewerFriend we might see > "error":{"code":501,"message":"Not Implemented"} > For Rest because it is a single call it seems we return NOT_IMPLEMENTED to > the whole request. > My question is - is this the correct way to deal with the case of partially > supporting a service? > Thanks > Justin > > > > _________________________________________________________________ > http://clk.atdmt.com/UKM/go/197222280/direct/01/ > Do you have a story that started on Hotmail? Tell us now >
