On 5/17/2011 10:12 AM, Micka wrote:
Well because I thought that hosting a java server application by Tomcat is
just perfect !
You can control a lot of thing, and you can create jsp page for
administration purpose.
Do you have better than Tomcat for hosting a java server application ?
I think what he's saying is that your app is duplicating a lot of what
Tomcat does, and it looks like it doesn't need tomcat at all (in other
words, it doesn't need to be hosted; it is its own server).
On Tue, May 17, 2011 at 4:03 PM, André Warnier<a...@ice-sa.com> wrote:
Micka wrote:
Thx for the advise, My mail will be better for the next time.
To explain better my application, it is a TCP server. And it received
connection requests from clients.
In my configuration I'm automatically waiting and accepting a connection
with :
java.net.ServerSocket.accept()
After that I give the socket to a Thread to communicate with the device.
In my case the device, works with commands. And to check if there is no
errors during the communication, It send me back an echo.
Each time that i send a command, I check if the echo is the same, if not,
I
create an Exception.
is that better ? :p
Yes, now it is starting to make sense.
The "devices" (which are not browsers), are actually TCP clients, but after
establishing a connection with the server (your application), they become
"passive" and wait for further commands from your Tomcat application.
:-)
So now, and purely by curiosity, whhy is your application then hosted under
Tomcat, if it is already its own TCP server and manages its own threads ?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org