Hi Ralf,
The release is planned so soon - so, can I assume that current git master is reasonably stable? I could then directly start using it, then I do not have to switch the REST interface later.
Yes, indeed I'd recommend to use our latest code base; there shouldn't be any major changes before the next release anymore. All differences between 6.7.1 and 6.8 should be marked in our Wiki (..search for "6.8").
Unfortunately, I can not send any <query> to the database due to the mime type restriction: I can not freely set the mime type, all I can do are POST queries with a mime-type of application/xml (at least I found no way to change that, I'll ask on the Orbeon mailing list). From all I read, that means I can not send POST queries to BaseX at all.
I see. One possible fix in BaseX/REST would be to get rid of the "application/query+xml" content type (we thought about that before) and treat XML input in another way; this would introduce some inconsistencies with earlier versions, but as we're currently switching to a new implementation anyway, this would a good moment. I'll have to spend some more thoughts on that first, however; let's see what the Orbeon guys say.
Actually I was quite surprised to see that POST can also be used to store documents, which I'd usually expect to be the behaviour of PUT - it seems the both are almost the same in BaseX?
We're following the RESTful sementics, as e.g. presented in Wikipedia [1]. While PUT is used to update existing resources, POST is applied to create or add new resources.
Hope this helps, Christian
[1] http://en.wikipedia.org/wiki/Representational_state_transfer#RESTful_web_ser...