Thanks for cogent reply, Chuck :) By socket servers, I mean the existing programs are bound to a particular port number and just sit there waiting for requests. The port numbers are arbitrary, and I'm not knowledgeable enough of networking to know whether they use HTTP or not.
I'll probably just write stand alone Java sockets servers and simply bounce incoming requests over to a servlet I'll develop to do the "heavy liffting". The reason I would have liked Tomcat to handle the whole shebang is that now I'll have to adjust each system that hosts these sockets to automatically invoke them when they restart. Kinda tedious. Thanks again On Wed, Jan 14, 2009 at 4:35 PM, Caldarale, Charles R < chuck.caldar...@unisys.com> wrote: > > From: Jonathan Mast [mailto:jhmast.develo...@gmail.com] > > Subject: Re: Can Tomcat be used to host socket servers? > > > > Not sure if dynamically rewriting server.xml is the way > > to go. > > Pretty much guaranteed not to be, since that would require stopping and > restarting Tomcat. > > > The situation is that we have some existing programs > > (written in C) that are socket servers. > > It's not clear to me exactly what you mean by "are socket servers". Do you > mean they simply do a listen/accept on a server socket, waiting for > connection requests from some client? If so, what protocol is being used? > If it's not HTTP (or AJP), Tomcat won't help you. > > Handling server sockets in Java borders on the trivial; using Tomcat just > for that would be massive overkill. > > - Chuck > > > THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY > MATERIAL and is thus for use only by the intended recipient. If you received > this in error, please contact the sender and delete the e-mail and its > attachments from all computers. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > >
