Markus KARG wrote:
> It is not essentially needed to interface to a physical storage (but it
> makes sense in 99.9% of all use cases): You could e. g. use my WebDAV
> contribution to have a WebDAV frontend but completely implement the
> processing inside of your JAX-RS resource (like checking temperature sensors
> or list them up as a result to a PROPFIND call; or list the IDs and
> positions of all GPS transmitters built into the car pool of your company).
> Not everybody has the demand to wrap a CMS/DMS, so my initial contribution
> targets in the frontend, while JCR or an SPI targets more in the backend.
> This is why I'd like to split efforts in these two distinct sections.
Understood, and you are of course right; these are different layers
inside a server implementation, and they should be clearly separated.
BR, Julian