Well, JK/JK2 are their own protocols, and the CoyoteConnector class handles them just fine. It even can handle SSL. Perhaps you could take a look at org.apache.coyote.tomcat4.CoyoteConnector and see if it will help you get a jump start on your own code.
John > -----Original Message----- > From: Yves Duhem [mailto:yves.duhem@;cryptolog.com] > Sent: Friday, November 15, 2002 4:03 AM > To: Tomcat Users List > Subject: Re: non Http connector > > > Thanks for your answer, > in fact I don't want to use http at all and I was wondering if it was > possible with tomcat. > I already have my own protocol, and since the communication will be > wrapped in ssl I don't need http. The only feature from http that I > might need is multiplexing. So I was wondering if the connector > architecture of tomcat allowed (without too much trouble) to > use another > protocol. > But it's true that using http is not a big problem and I'll > probably end > up doing that. > yves > > Milt Epstein wrote: > > On Thu, 14 Nov 2002, Yves Duhem wrote: > > > > > >>Hi, > >>I would like to use servlets and tomcat without having to > communicate > >>via http. > >>my request's first line would indicate in some way the > target servlet > >>and the rest would be the data to transmit to the servlet > >>the response would be only the data (no headers). > >>(and all this would be used with SSL.) > >> > >>I would like to know if a connector behaving like this > exists somewhere, > >>or if i'll have to modify one of the existing connectors > (and in that > >>case is there any developer documentation about the > connector framework?). > > > > > > Are you saying that you really don't want to use HTTP (as a > protocol), > > or just that you want to do this outside the context of a > web browser? > > Because in the current HTTP framework there's nothing > that's stopping > > you from using it outside of a web browser. You can, for > example, set > > up a java application that opens a URLConnection to a Tomcat server. > > You can even transfer objects this way (to a certain degree) instead > > of just parameters, because you'll have direct control of > > reading/writing the I/O streams. > > > > I'm not really sure what not using HTTP buys you, because > then you're > > essentially creating your own client/server system and defining your > > own protocol, and you have to set everything up. If you > use HTTP, you > > get a lot essentially "for free" (including parameter passing, > > sessions, cookies, ssl, etc.) > > > > Milt Epstein > > Research Programmer > > Integration and Software Engineering (ISE) > > Campus Information Technologies and Educational Services (CITES) > > University of Illinois at Urbana-Champaign (UIUC) > > [EMAIL PROTECTED] > > > > > > -- > > To unsubscribe, e-mail: <mailto:tomcat-user-unsubscribe@;jakarta.apache.org> > For additional commands, e-mail: <mailto:tomcat-user-help@;jakarta.apache.org> > -- To unsubscribe, e-mail: <mailto:tomcat-user-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:tomcat-user-help@;jakarta.apache.org> -- To unsubscribe, e-mail: <mailto:tomcat-user-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:tomcat-user-help@;jakarta.apache.org>
