Thanks Bill... ok I can kinda see it... ha ha
I imagine a SP would look at it very carefully, more so than our typical
application which is
intranet and nowhere near massive volumes...
The holding connections is interesting.... heres possibly a crazy scenariao,
do you think this
is possible and because I'm throwing it out there maybe one has to assume
its on a generic servlet...
If say one had remote video camera's pumping out IP packets... and a number
of security
surveillance stations... so the camera's are continously pumping packets,
and users can connect
and view.... that breaks the typical Http type model.... with these NIO
sockets... possible
do you think? ie holding the input sockets and feeding the users sockets as
fast as possible, perhaps sometimes dropping packets on purpose...
monitoring buffers etc...
.... there I can see the threads are controlled directly and the connections
are still held?
Could TC NIO do that... taking for granted protocols? ...
This NIO gives me a "piping" feel... if you know what I mean... I look at it
and think, well if I emulate
the buffer control that TC does damn well already... what for, but if I need
to "bridge" things... it looks kinda
cool... or if the client or server deviates too much from question -> answer
<- which I think is what you also
saying with the soap thing... maybe?
----- Original Message -----
From: "Bill Barker" <[EMAIL PROTECTED]>
To: <users@tomcat.apache.org>
Sent: Saturday, February 23, 2008 5:58 AM
Subject: Re: NIO Java or TC - What are u using it 4?
Well, you need it for Comet (unless you use the APR Connector which has
similar functionality). I have a project that hasn't moved to Comet yet,
but probably will do sometime this year, since the prototypes show a lot
of promise. With Comet, you are basically setting up long-lived
connections with the option of server-push (so you have some protocol
wrapped in HTTP, e.g. SOAP), that needs to run for a long time before
producing results.
You also get 'sendfile' support, so if your site sends a lot of very large
static files, you can win this way (mostly the reason to use it on
Windows).
Even with conventional Servlets, you can get a benifit for high-volume
sites. But this depends on your OS, how much hardware you want to give
it, and your Java vendor. Using the NIO Connector means that threads
aren't tied up waiting on HTTP Keep-Alives, so if the cost of having 5000
threads blocking on input is high for you (e.g. true for Linux systems
with older kernals), then the NIO Connector can lower your cost. For
Solaris with Sun's JVM, Sun has implemented NIO better than APR has, so it
should be a no-brainer.
Like with most things, profile it against the app that you are actually
using. That is the only way to know for sure if it is right for you ;).
"Johnny Kewl" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
Cant contain my curiousity anymore?
What practical applications is this been used for?
I see theres a lot of control over the socket etc... but what are you guys
actually doing with it?
Trying to get rule of thumb for when one would move to it?
---------------------------------------------------------------------------
HARBOR: http://coolharbor.100free.com/index.htm
The most powerful application server on earth.
The only real POJO Application Server.
Making the Java dream come true.
---------------------------------------------------------------------------
---------------------------------------------------------------------
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]
