[infinispan-issues] [JBoss JIRA] (ISPN-8529) REST Cache create and remove

[Tristan Tarrant (JIRA)]

     [ https://issues.jboss.org/browse/ISPN-8529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tristan Tarrant updated ISPN-8529:
----------------------------------
    Description: 
Implement cache creation/removal over HTTP.
Since WebDAV (RFC-4918) describes operations over "collections", we can reuse the semantics of invocations and error messages. In particular:

https://tools.ietf.org/html/rfc4918#section-9.3
https://tools.ietf.org/html/rfc4918#section-9.6.1

Cache creation:

*MKCOL /{cacheName}[?template={template}]*
This will create the named cache, using the optionally supplied template name for configuration. If a template is not specified, then the configuration of the default cache defined on the cache container will be used.

Cache removal

*DELETE /[cacheName]*
This method's behaviour is affected by the presence and value of the `Depth` header.
The header can have the following values:

* infinity,noroot: deletes the contents of the cache. This is the default behaviour (for backwards compatibility this does not respect the behaviour described in link:https://tools.ietf.org/html/rfc4918#section-9.6.1[WebDAV RFC] regarding removal of collections). If successful this operation returns a status of 200.
* infinity: removes the cache from the system. If security is enabled, you will need ADMIN permissions. If successful, this operation returns a status of 204 (No Content). This method also understands <<rest:adminflags>>


  was:
Implement cache creation/removal over HTTP.
Since WebDAV (RFC-4918) describes operations over "collections", we can reuse the semantics of invocations and error messages. In particular:

https://tools.ietf.org/html/rfc4918#section-9.3
https://tools.ietf.org/html/rfc4918#section-9.6.1

Cache creation:

{{MKCOL /{cacheName}[?template={template}]}}
This will create the named cache, using the optionally supplied template name for configuration. If a template is not specified, then the configuration of the default cache defined on the cache container will be used.

Cache removal

{{DELETE /[cacheName] }}
This method's behaviour is affected by the presence and value of the `Depth` header.
The header can have the following values:

* infinity,noroot: deletes the contents of the cache. This is the default behaviour (for backwards compatibility this does not respect the behaviour described in link:https://tools.ietf.org/html/rfc4918#section-9.6.1[WebDAV RFC] regarding removal of collections). If successful this operation returns a status of 200.
* infinity: removes the cache from the system. If security is enabled, you will need ADMIN permissions. If successful, this operation returns a status of 204 (No Content). This method also understands <<rest:adminflags>>




> REST Cache create and remove
> ----------------------------
>
>                 Key: ISPN-8529
>                 URL: https://issues.jboss.org/browse/ISPN-8529
>             Project: Infinispan
>          Issue Type: Feature Request
>          Components: Remote Protocols, Server
>            Reporter: Tristan Tarrant
>            Assignee: Tristan Tarrant
>             Fix For: 9.2.0.Final
>
>
> Implement cache creation/removal over HTTP.
> Since WebDAV (RFC-4918) describes operations over "collections", we can reuse the semantics of invocations and error messages. In particular:
> https://tools.ietf.org/html/rfc4918#section-9.3
> https://tools.ietf.org/html/rfc4918#section-9.6.1
> Cache creation:
> *MKCOL /{cacheName}[?template={template}]*
> This will create the named cache, using the optionally supplied template name for configuration. If a template is not specified, then the configuration of the default cache defined on the cache container will be used.
> Cache removal
> *DELETE /[cacheName]*
> This method's behaviour is affected by the presence and value of the `Depth` header.
> The header can have the following values:
> * infinity,noroot: deletes the contents of the cache. This is the default behaviour (for backwards compatibility this does not respect the behaviour described in link:https://tools.ietf.org/html/rfc4918#section-9.6.1[WebDAV RFC] regarding removal of collections). If successful this operation returns a status of 200.
> * infinity: removes the cache from the system. If security is enabled, you will need ADMIN permissions. If successful, this operation returns a status of 204 (No Content). This method also understands <<rest:adminflags>>



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)