- From: Conal Tuohy <conal.tuohy@gmail.com>
- Date: Wed, 13 May 2015 09:54:39 +1000
- To: Florent Georges <fgeorges@fgeorges.org>
- Cc: XProc Dev <xproc-dev@w3.org>
- Message-ID: <CAErBQuSOhya_tYfcoDUF-ogTjvU27L64oWPQ74RDJrcK-K1xCQ@mail.gmail.com>
Hi Florent! Yes XProc-Z is in many ways like Servlex or Piperack or similar server platforms. The key difference I think is the way in which the XProc pipeline is connected to the HTTP protocol. If I understand it correctly, in Servlex the HTTP request is parsed into a sequence of XML documents of a custom (Servlex-defined) type, which are passed to a pipeline. In other words, the HTTP protocol is converted into a custom protocol for connection to the pipeline. Whereas when XProc-Z receives an HTTP request, it passes it to the pipeline in the form of a c:request document, to which the pipeline is expected to respond with a c:response document. In other words, an XProc-Z pipeline uses XProc's own "native" HTTP protocol binding, just like the p:http-request step. Regards Conal PS Straight after posting that release, I discovered a regression error in the downloading of binary files (base64 decoding) which I'm now fixing, while kicking myself for not having a proper test suite. On 12 May 2015 at 18:26, Florent Georges <fgeorges@fgeorges.org> wrote: > On 12 May 2015 at 03:43, Conal Tuohy wrote: > > Hi, > > > I have made a beta release of XProc-Z; the simple web platform for XProc. > > Great to see more happening in this area! > > > The major point of difference between XProc-Z and other XProc-hosting > > servers is that in XProc-Z, a web application is entirely defined in a > > single XProc pipeline. > > Sounds like what Servlex is doing (among other possibilities), doesn't > it? > > Regards, > > -- > Florent Georges > http://fgeorges.org/ > http://h2oconsulting.be/ >
Received on Tuesday, 12 May 2015 23:55:26 UTC