I definitively have no such plan, it was just an idea how we could deal with
your ideas. I just want to provide my "pure" WebDAV stuff, and somebody
likes to define such an SPI later, he can do that. I do not see any
relationship, actually.
Regards
Markus
From: Daniel Manzke [mailto:daniel.manzke_at_googlemail.com]
Sent: Montag, 8. Dezember 2008 10:31
To: dev_at_jersey.dev.java.net
Subject: Re: [Jersey] JAX-RS based WebDAV support
Sounds for me like a plan? :)
This is the way I wanted to go at the beginning of the discussions. To have
the "generic" WebDAV implementation for JAX-RS. So everybody could implement
WebDAV support for his application. And as a nice addon, we could try to
create some kind of a SPI in the backend or delivery standard solutions for
JCR, JPA or FS.
Daniel
2008/12/7 Julian Reschke <julian.reschke_at_gmx.de>
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_jersey.dev.java.net
For additional commands, e-mail: dev-help_at_jersey.dev.java.net
--
Mit freundlichen Grüßen
Daniel Manzke