Sean, > We had a similar issue and I think this is an area where the REST philosophy > is somewhat stressed. < [..] > We decided to make a web service, use a POST and put the criteria in the > XML. Then the URI could be /accounts/search which is pretty easy to > deal with.
I'm not sure it stretches the REST philosophy. POSTing a search criterion makes sense if you want to cache a cursor on the server side, for instance. You could do this: POST /accounts/search balanceLesstThan=2000 status=active The serve returns: http 2001 created location:/accounts/cursor/121212 The server keeps the open cursor in the cache for a limited amount of time. You access it with: GET /accounts/cursor/121212?page=2 This is on the salesforcers.com search API works. -Vincent.
