- From: Leif Warner <abimelech@gmail.com>
- Date: Tue, 2 Jun 2009 11:51:27 -0700
- To: Norman Walsh <ndw@nwalsh.com>, XProc Dev <xproc-dev@w3.org>
- Message-ID: <54d4ec0f0906021151q675a3c69rab455fbafd0900d7@mail.gmail.com>
Well, I could try loading the source pipeline from a http: URI, then? Eventually I was hoping to hack on it to get it to load the pipeline from an in-memory blob (string?); running as a web service it seems wasteful to write a POSTed pipeline out to disk before running it. Perhaps the pipeline to be run could be passed in on stdin in the source input port, and a default base pipline could then eval that... -Leif On Tue, Jun 2, 2009 at 11:39 AM, Norman Walsh <ndw@nwalsh.com> wrote: > Leif Warner <abimelech@gmail.com> writes: > > I was wanting to run Calabash behind a web service that has the > > pipelines generated and fed into it from a Javascript pipeline GUI > > tool. For this, I would want to restrict pipelines from writing to the > > filesystem (other than temp), and running arbitrary commands. I can't > > seem to get calabash -S (safe mode) to run on anything, though; it > > just gives a dynamic error about access to that resource not allowed > > on simple pipelines like say, the included pipeline.xpl test pipeline. > > Oh, dear. I've made it just a little too restrictive, haven't I? > It won't even load the source pipeline from a file: URI. > > I'll try to fix that for the next release. > > Be seeing you, > norm > > -- > Norman Walsh <ndw@nwalsh.com> | 'I have done that,' says my memory. 'I > http://nwalsh.com/ | cannot have done that'--says my pride, > | and remains adamant. At last--memory > | yields.-- Nietzsche >
Received on Tuesday, 2 June 2009 18:53:03 UTC