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. The bug fixing was/is part of that learning process.
(Side note: The AJP13 protocol docs were, in fact, very good - good enough that I was able to write 95% of the java-side of the connector without reading the source code for the tomcat connector. It wasn't until the last stages of debugging that I looked at the source. Well done to whoever wrote those.)
I expect it would be good for people who just want to distribute an extra jar with their webapp to make it deployable. Kind of like a no-brainer/no-frills deployment case .... easy, works, but if you want more features, use something more sophisticated. If that's the kind of alternate container you're looking for, I'm all ears.
I had missed the reply, sorry for the late answer.
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 could become an alternative to Catalina (I know the idea floated around on a few occasions in the past).
Rémy
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
