From: Andrzej J. T. <an...@ch...> - 2007-09-07 23:30:40
|
Adam: > So if I understand this, basically you want to allow HTTP Methods other > than GET/POST to reach an XQuery, so that the XQuery can be the processing > mechanism? Exactly so! > Well an interesting idea indeed and not a bad one :-) ;-) > But, I think it fits into a larger piece of work, that I started sometime > ago... > > I started refactoring the HTTP aspects of eXist, this included a completely > new Servlet and REST architecture, (no XQueryServlet, no Cocoon embedded) a > 1/2 finished version of this is available in branches/adam. I had some issues > with URI resolution with regards XSLT and XInclude that I needed to fix, > Dannes has subsequently done some serious work on URI resolution in eXist, > which should allow this to be moved forward further. Ah...I didn't know that. Sounds like it's not worth moving ahead with my idea till this prerequisite work is completed. > So, I would like to revive this work and add some additional concepts that > have come to light recently - Agreed. > 1) A few additional REST parameters to support XQJ (i.e. > mashalling/de-marshalling of XML and type information, and Query > cancellation) 2) Streaming throughout (needed for Query cancellation and also > better efficiency for queries that generate huge result sets) 3) And of > course, what you have just mentioned... Sounds good to me. > If your interested we could discuss this in more detail and plan a way > forward... Yuppers! Not sure how much time I'll have to devote to this over the next couple of months though....got some critical client deadlines that are going limit my discretionary coding capacity. Andrzej Jan Taramina Chaeron Corporation: Enterprise System Solutions http://www.chaeron.com |