Martin Grotzke wrote:
>>> To give an example: we have a user resource, and it shall be
>>> possible to
>>> change the password for the user. So now I would prefer to provide a
>>> POST to /users/{username}/password.
>>>
>> PUT would be more appropriate, as you are updating.
> We require oldPassword, newPassword and newPasswordRepeated for the
> update, so I thought it should be POST. Am I wrong with this?
>
Ah, i see, yes in this case POST makes sense.
>> I am wondering if it may be possible to automatically derive at
>> runtime some hierarchy from XML schema or JAXB beans to help automate
>> this type of thing...
> Do you mean, that if some conventional structure (information) is
> provided, that then some resource would be provided automatically?
Yes. I need to go back over MS's RESTful Robotics but i think it does
that type of thing.
> Or
> what else do you have in mind?
>
--
| ? + ? = To question
----------------\
Paul Sandoz
x38109
+33-4-76188109