Why you are sayinig that a container cant support more than one protocol ?
it future it can be right ?
I want to implement a new protocol .. Not for commercial purposes but for study alone :-)
Before implementing , i thought it would be nice if i can understand the architecture of Tomcat ...
"Servlets are very specific to HTTP " -Can you alaborate on this ..
"But I wouldn't be doing you a favor to
give you the link, even if I had it sitting around" -- Why ? Come on :-)
Do you think that implenting a new protocol is not a good idea ?
Regards
Jwas
| "Christopher K. St. John" <[EMAIL PROTECTED]>
Sent by: "A mailing list for discussion about Sun Microsystem's Java Servlet API Technology." <[EMAIL PROTECTED]> 06/05/02 10:53 AM
|
To: [EMAIL PROTECTED] cc: Subject: Re: GenericServlet & HttpServlet |
"[Jwas J]" wrote:
>
> Suppose if the servlet container supports another protocol
>
In practice, containers only support HTTP, so the question is
theoretical. That's ok, just keep in mind it's all pretty much
speculation at this point.
> If the client is using XXX then the XXXServlet (similar to
> HttpServlet)'s service method is called ... Is my concept
> correct ?
>
Yep, that would be the basic theory. You're not thinking
of implementing this, are you? The pattern so far seems to
be that somebody gets all fired up about adding a new
protocol, starts coding, discovers that Servlets are really
very HTTP specific in unobvious ways, and then gives up.
That said, the SIP people seem to think it's a good
idea, so check the current set of JCP's for SIP servlets.
And I think there was an Apache project to add mail
processing (or something?) to the api, but I forget the
name (I'm sure somebody will correct me)
Note that I'm not saying it's necessarily a bad idea,
just that noone seems to have been wildly successful at
it so far.
> Where can i get the class diagram or Technical diagram of
> Tomcat ? is it available in the net ?
>
Yeah, kind of. But I wouldn't be doing you a favor to
give you the link, even if I had it sitting around. The
internals documentation is the code, and pretending
otherwise is counterproductive. If you read through
the "Config Reference" you'll get the idea, since the
internal processing matches up with the object structure
set up in server.xml.
Jetty is smaller and arguably easier to understand
if you just want to see how a "real" container works.
> Also regarding the connectors , it would be nice if some
> one can provide info regarding the part of tomcat which
> populated the request , response object before calling the
> public method service .
>
Use the source, luke. (Hint: org.apache.catalina.connectors
is a good place to start. Hint #2: It all changes between
Tomcat 4.0 and Tomcat 4.1)
Discussion of Tomcat internals is probably more appropriate
for tomcat-user or tomcat-dev.
--
Christopher St. John [EMAIL PROTECTED]
DistribuTopia http://www.distributopia.com
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
