On 27.03.2008 13:25:16 Jason Timmins wrote: <snip/> > > I'd pack Saxon and FOP together into a web service. That way you don't > > have the VM startup each time. > > That'd be a web service written in Java I guess. Sadly, that's not an > environment I'm comfortable with.
Ok, that can make things a little more complicated. > Also, don't the processes associated with answering web services calls (as > it were) come and go each time? A call comes in, Java fires-up, sends a > responds and then Java goes away. Sounds like I'd hit the same kind of > start-up delays I was getting initially. Admittedly, my app would be firing > requests at the web service in quick succession so Java might not come and > go each time. (This is really at the limit of my knowledge on such things!) Not at all. You'd bring up a web container (such as Jetty or Tomcat) up as a server process. The web container is multi-threaded and the web service would be deployed in that web container. After the first or second call to the webservice all Java byte code has run through the JIT compiler and all classes will have been loaded. By then you'll have very high response times. Even the threads will be pooled. <snip/> Jeremias Maerki --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
