Xavier Franc wrote: Hi Xavier,
> - access to HTTP headers etc is not something that we consider > in XQS. For tsuch features, we are thinking of another > interface not yet published, similar to what exists already > in other products. > We call it 'XQuery WebApps' or 'XQuery Server Pages', and it > would be HTTP oriented, Great! Sounds like the EXPath Webapp module. I a few words, this module defines 1) an explicit mapping between the request URIs and X* components (XProc, XSLT or XQuery) and 2) an XML format for HTTP requests and responses. When a request is sent to the server, it looks for a component with a URI pattern matching the request URI (the pattern is an XPath regexp). It then transforms the request to the XML format (like in http://h2oconsulting.be/tools/dump) and calls the component with this request element. Unfortunately this is still a work in-progress, and there is no spec yet. But there is an open-source implementation named Servlex available at http://code.google.com/p/servlex/. E.g. the following websites are powered by Servlex: http://expath.org/ and http://h2oconsulting.be/. You can see what the request elements look like by having a look at http://h2oconsulting.be/tools/dump (for instance by using the form at http://h2oconsulting.be/tools/form for some variations). This URI is implemented by a simple stylesheet that dumps to HTML the request element it receives from Servlex. > [it would be HTTP oriented,] while XQS would be similar to Web > Services (but much simpler). I see. The approach I followed with the Webapp module it to define a mapping between HTTP and X* components. This is of course low-level, but at least it provides a full mapping, and brings all the HTTP information to the XML level, without making any assumption. Such a mapping is probably complex enough to deserve its own spec. The goal is to have a robust low-level but powerful layer, on top of which it is possible to create other projects, more specific but entirely written themselves in XML technologies (like a general-purpose web MVC framework based on file name conventions and supporting XForms, or a Web Services framework to implement Web Services on the server-side, etc.) > I hope we can discuss these topics more deeply later. I'd be glad to have a chance to discuss those concepts more deeper, both to hear your comments about EXPath Webapp and to discuss what I've learned since I started working on it. Regards, -- Florent Georges http://fgeorges.org/ -- Qizx Support List [email protected] http://www.xmlmind.com/mailman/listinfo/qizx-support
