Jerome Louvel schrieb:
> Julian,
>
>> one issue is whether the implementation is supposed to handle all
>> request headers contributing to the preconditions (keep in
>> mind that the
>> set is open-ended, for instance RFC2518 adds "If" and "Overwrite").
>
> Thanks for the pointer, this is an interesting extension case. I'm not sure
> if the implementation of a compliant WebDAV server *fully* falls into the
> scope of JSR-311.
>
> JSR implementations could simply provide mechanisms to extend their
> preconditions check logic. In the Restlet API it is already possible, and
> I've entered an RFE to consider simplifying this use case even more:
> http://restlet.tigris.org/issues/show_bug.cgi?id=284
>
> Best regards,
> Jerome
Jerome,
I do agree that it's up to the EG to decide what the goal is. As far as
I am concerned, I think the API should make it dead easy to write good
rest-based services, but there should be extension hooks for those who
need to go beyond that.
Maybe we should start to compile a list of extension points we need to
consider?
- method names
- header types (syntax: list, precondition checking, entity header,
character escaping...)
- status codes
...and so on...
Best regards, Julian