M Group
> Antworten an: [EMAIL PROTECTED]
> Datum: Mon, 6 Jan 2003 12:28:50 -0400
> An: [EMAIL PROTECTED]
> Betreff: Re: [JBoss-user] Non-HTTP Servlets?
>
> El Lunes 06 de Enero del 2003 10:06 AM, Muntean Horia escribió:
>> Do you really need other protocol than HTTP?
>
>
El Lunes 06 de Enero del 2003 10:06 AM, Muntean Horia escribió:
> Do you really need other protocol than HTTP?
Unfortunately, yes. I am porting legacy C code that uses a proprietary
protocol. We are not touching the clients, so moving to HTTP is not an
option.
> So why not keep all the benefit
Rodrigo Chandía wrote:
Hi Everyone:
Can Servlets be used to handle protocols other than HTTP?
I have to handle a protocol other than HTTP in a request/response fashion so
I thought servlets would be a nice way to do it. I guess that an application
server can handle connections, threads and su
f the Java Web Server or JSDK or something..
James
> -Original Message-
> From: James Higginbotham
> Sent: Thursday, January 02, 2003 10:34 PM
> To: [EMAIL PROTECTED]
> Subject: RE: [JBoss-user] Non-HTTP Servlets?
>
>
> > Yes, this is quite standard. Use G
> Yes, this is quite standard. Use GenericServlet as your base class.
That's cool.. You or anyone else remember if there is a deployment
descriptor to indicate the port to bind to? Its been a looong time since
I've looked at anything but HTTPServlets, but this thread sparked my
interest once agai
> -Original Message-
> From: Rodrigo Chandía [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, January 02, 2003 7:02 PM
> To: [EMAIL PROTECTED]
> Subject: [JBoss-user] Non-HTTP Servlets?
>
>
> Hi Everyone:
>
> Can Servlets be used to handle protocols other than HTTP?
Yes, this is quite sta
Rodrigo Chandía wrote:
Hi Everyone:
Can Servlets be used to handle protocols other than HTTP?
I have to handle a protocol other than HTTP in a request/response fashion so
I thought servlets would be a nice way to do it. I guess that an application
server can handle connections, threads and suc
