Re: [Exist-open] How best to do HTTP Put/Delete handled by xquery?

[coach3pete <coa...@gm...>]

+1 
This may be the better long term solution. Although it looks like the two routes at present would only differ in the doPut and doDelete methods, it may be desirable to allow these to evolve independently: one is about modifying db resources, the other /xquery gives full control over handling requests. What does it take to add another service like this to exist? I can pitch in to give it priority if needed.
Best,
Erik


On Jan 23, 2010, at 11:06 AM, Andrzej Jan Taramina wrote:

> Wolfgang:
> 
>> it looks like you are experiencing the same problem as Erik (see the
>> "update delete removes .xqy file" thread). We will need to change the
>> REST server to add a possibility to overwrite the default behavior.
> 
> I don't consider it a "problem" as much as a feature enhancement though. ;-)
> 
> The REST server works just fine given the specifications.
> 
> I was thinking that if we designated/implemented support for a new url structure, replacing the /rest with /xquery,
> where the latter would always have the semantics that it would execute the xquery regardless of HTTP verb, that would be
> a very clean way of doing it, without any backwards compatibility issues with the /rest urls.
> 
> How hard would that be to accomplish?
> 
> Thx!
> 
> -- 
> Andrzej Taramina
> Chaeron Corporation: Enterprise System Solutions
> http://www.chaeron.com
> 
> ------------------------------------------------------------------------------
> Throughout its 18-year history, RSA Conference consistently attracts the
> world's best and brightest in the field, creating opportunities for Conference
> attendees to learn about information security's most important issues through
> interactions with peers, luminaries and emerging and established companies.
> http://p.sf.net/sfu/rsaconf-dev2dev
> _______________________________________________
> Exist-open mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-open