I understand what you are saying, however that means you also have to
re-do all the "application management" system. Deployment,
connectors, management, adminstration, thread management, load
balancing, SSL key management and configuration and many many other
infrastructure pieces that can be leveraged to manage a large complex
system. This would be a huge project (ie: the scale of creating tomcat)
So if one wants to create a web adminstratable application that has
(one or more servlet "ports" that connect with other protocols). And
has web ports to handle HTTP requests into the same system. If you
*can* do it in tomcat it would be great. If those protocols are
somewhat "transaction" based then they would fit very well into the
servlet model. I am trying to sus out the potential.
Yes you can always write a complete application manager from scratch :)
I am trying to avoid it.
Peter K.
At 06:36 2/28/2007, Georg Sauer-Limbach wrote:
If you don't want to deal with HTTP, you should
not use the Servlet API (which is the Java
abstraction of HTTP) at all. You can do the
indicated code with generic sockets, no need to
mind about Servlets altogether.
Georg
Peter Kennard wrote:
Ok - continuing.
Is it possible to use a "GenricServlet" to do basicly this.
service(req,res)
{
for(;;)
{
readSome(req.getInputStream());
if(writeSome(req.getOutputStream()) {
req.flushBuffer();
} else {
break;
}
}
}
That is read in incomming "socket stream" and write something back
while reading in a way that takes advantage of the
connection. That is not being purely "transactionless" and
bypassing all the HTTP specific protocols after the header needed
to address the specific servlet.
PK
At 20:59 2/27/2007, you wrote:
I guess I'll answer my own question here after some testing and research
That is:
If you override the "service()" method on servelet all you need
is a "service name" and a "path" to the servlet followed by two
newlines as the "minimal" header.
ie:
X /Z\n\n
for the most minimal header.
"X" being the service name and "/Z" being the path to the servlet.
On reply if "service()" if you write to the
response.getOutputStream() you are in essence writing directly to
the connected socket unfiltered.
At 18:32 2/26/2007, you wrote:
Was this last message of mine just too naive :)
Should I break it into smaller parts?
Still curious :)
Peter K.
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
