api comment

michael

unread,

Nov 23, 2009, 9:51:25 AM11/23/09

to reststar-caching

* What about POST /{cacheName} for when the client does not care about
the key?
the implementation could be a uuid

* should custom headers not start with X-?

Michael

Manik Surtani

unread,

Nov 23, 2009, 10:00:23 AM11/23/09

to reststar...@googlegroups.com

On 23 Nov 2009, at 14:51, michael wrote:

> * What about POST /{cacheName} for when the client does not care about
> the key?
> the implementation could be a uuid

As in, the POST call could respond with a generated key? Sure, that makes sense for cases where you don't care about the key.

--
Manik Surtani
ma...@jboss.org
Lead, Infinispan
Lead, JBoss Cache
http://www.infinispan.org
http://www.jbosscache.org

michael

unread,

Nov 23, 2009, 10:04:51 AM11/23/09

to reststar-caching

yes
201 + Location header

actually, HTTP requires this if a resources has been created

Michael

Michael Neale

unread,

Dec 1, 2009, 10:48:28 PM12/1/09

to reststar-caching

yes that would be a good idea.

For Infinispan I simply expected a key name to be there as part of the
path (echache does that - and in its case I think a POST to a cache
name would imply some settings? but that is a bit odd).

Reply all

Reply to author

Forward