Ulrich,
Here's a paragraph I just posted to cocoon-dev:
95% of what I need is a block that does XML-->XSL(FO|T). I have many
server-side apps, who would love to use this block. Why should they make
a costly HTTP connection to some server that runs Cocoon and commit to
the interfaces Cocoon prescribes? Wouldn't it be much cooler if I used
the "XML-->XSL(FO|T)" block from Cocoon and keep everything within the
framework and on the same JVM?
My obsevation.... Very well put request. Id modify it to say:
"XML/XSP-->XSL(FO|T)"
I could even run a HTTP/Servlet server under Phoenix (e.g. Jo!) and have it use Cocoon's blocks for doing XML stuff - no costly TCP connections to some servlet engine anymore.
Spooky. Great minds think alike. Err, promoting my mind perhaps ;-)
Incidenatlly there would be a TCP/IP request, but (never fully answered) how far does it leave the virtual machine in host-OS before it re-enters the same VM for handling.
Regards,
- Paul H
-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
