Daniel Manzke wrote:
> The last ones are:
> There was an idea for webdav support. Due my work with the JCR /
> JSR170+JSR283 I asked how to solve some kind of recursive structures.
> Because with the JCR you can create some kind of a tree and it's hard to
> solve this with rest.
IMHO this is nothing to do with the REST style and more about how you
define your service. WebDAV solves it by defining it's own uniform
interface that extends that of HTTP. I have experimented with recursive
AtomPub feeds, it worked out OK. There are issues but they don't appear
to be insurmountable if the server clearly specifies the relationship (a
general interoperable solution may be harder to get agreement on).
> Stefan told us of some spacers like ** or so on. I
> will looking forward.
> A very good choice for using the JCR api is webdav,
I agree, another could be AtomPub (for a subset).
> because of the ability
> to handle the repository like a filesystem. Due my lack of knowledge of the
> webdav protocol an simple example would be very nice and I thing a big
> "marketing point" for the restful services. Stefan was some kind of
> interested in that, but I had no time after the presentation to fix this
> idea.
>
In principle one could use the client API. But i think it would be
better to extend the API with specific semantics of the additional HTTP
methods that WebDAV specifies. I have not investigated if it is possible
to easily do this with the Jersey client API. It would be interesting to
try if i had the time!
>
> So enough spam.
>
> Again, a BIG thank you for the presentation and a BIG thank you for this
> nice API.
>
Thanks!
Paul.
--
| ? + ? = To question
----------------\
Paul Sandoz
x38109
+33-4-76188109