Remy,
So now that you have learnt, are you more ineterested in using the TC
connectors ? Casually looking at the HTTP code, I can say it is not
especially efficient (and really optimizing this part is rather long
and painful).
If you want to join this project, your servlet API implementation
Rick Knowles wrote:
It was mainly a case of doing something so I could learn how it really
worked and why - I didn't consider using Coyote mainly because the http
request/response parsing was an important part of the understanding
process, and I didn't want to miss out on the details of that.
Hi,
I'm currently working on embedding a jasper engine within a servlet
container that I'm writing. During this work I have run into the
following questions:
1) Is the only advantage to using fork=true, that the javac memory leak
issue is avoided?
2) Has the javac memory leak issue been
Dennis,
I'm not a tomcat dev, but hopefully I can help anyway - having done what
I think it is you're trying to do. I did mine for the Winstone servlet
container (http://winstone.sourceforge.net)
For Nos 1 and 2, I can't help. But for No 3 it involves setting context
attributes:
1)
Rick Knowles wrote:
Dennis,
I'm not a tomcat dev, but hopefully I can help anyway - having done what
I think it is you're trying to do. I did mine for the Winstone servlet
container (http://winstone.sourceforge.net)
For Nos 1 and 2, I can't help. But for No 3 it involves setting context
Dennis Thrysøe wrote:
Hi,
I'm currently working on embedding a jasper engine within a servlet
container that I'm writing. During this work I have run into the
following questions:
1) Is the only advantage to using fork=true, that the javac memory
leak issue is avoided?
2) Has the javac
Rick Knowles wrote:
Dennis,
I'm not a tomcat dev, but hopefully I can help anyway - having done what
I think it is you're trying to do. I did mine for the Winstone servlet
container (http://winstone.sourceforge.net)
Interesting. Any reason for writing your own connectors (assuming you
do),
