(forgot to CC list in first mail, sorry)
Hi again,
you can be lucky, we've just realized another one of your feature requests. Your feedback is quite helpful indeed, as you're currently the first active external tester of our integrated REST implementation ;)
I'm glad if I can help ;-) . The REST API looks good overall, the only thing I do not like about it is the special content-type it needs (I sent a pull request for a bugfix that was necessary to make it entirely work here).
I did not get any reply from Orbeon (usually, Erik checks the list once or twice a week). For now I patched Orbeon myself to support that content type when the serialization setting of the XForms submission is set accordingly. But maybe there is a better solution, one that uses some property of the request URI to distinguish POSTED data from POSTED queries, instead of the content-type? For example, I don't think POSTing to a URL like /rest/collection?query makes much sense if you want to store a file - is the ?query ignored (then it could instead be used as indicator that this is NOT a request to store data), or should it get part of the filename (which would be quite surprising). The only problem I see is that POST a <run>...</run> to ?query or ?command does not make much sense, IMHO that should be considered an invalid request. I attached a completely untested draft patch of what I meant. But then, I do not know the reasons for why the interface looks the way it does, so maybe my suggestion is completely against your intentions ;-)
Kind regards, Ralf
On Thursday 22 September 2011 20:48:54 you wrote:
Is that a regression?
Whoops.. no, that was a bug, which is now fixed.
Sorry, Christian