Hi Adam,
Sounds good. eXist-db has various modules e.g. http://exist-db.org/exist/functions/request that can be used to fill in the gaps in RestXQ as currently defined. BaseX starts with an almost blank sheet. Multipart would be good, and also the @context parts of jax-rs.
/Andy
Yes that sounds good, im actually working on it right now.
I am trying to finish the implementation in eXist-db and have also
spent some time to try and pull it out into a set of libraries without
implementation specific parts, but there is still more to do there.
I then hope to write up the draft specification and get it to Balisage
for late-breaking news, but we will have to see. Either way, comments
and input are welcome :-)
Hope you are both well?
Cheers Adam.
--
On 6 May 2012 17:45, Christian Grün <christian.gruen@gmail.com> wrote:
> Hi Andy, hi Adam,
>
>> I understand the restxq stuff is in development/experimental and I wonder
>> what plans you have in that direction?
>> I think there are issues/limitations with the url limited to restxq/ and
>> that xqm can be accessed directly (as text) etc, but one limitation of the
>> spec seems to be that one can read a named header or cookie ( chosen at
>> design time ) but not list all headers in the request.
>> I wonder if an extension to get the full serialization of the request in the
>> http:send-request response format might be useful. e.g.
>> %rest:request("{$req}")
>
> maybe we can start some join discussion on the future of RESTXQ?
> Christian
Adam Retter
skype: adam.retter
tweet: adamretter
http://www.adamretter.org.uk