-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Igor,
On 5/24/16 6:52 PM, Igor Cicimov wrote:
> On 24 May 2016 12:33 pm, "Christopher Schultz"
> wrote:
>>
> Jakub,
>
> On 5/23/16 8:03 PM, Ja kub wrote:
Christopher, Thx for response, pleas confirm or deny if I
understand well.
>>
On 24 May 2016 12:33 pm, "Christopher Schultz"
wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Jakub,
>
> On 5/23/16 8:03 PM, Ja kub wrote:
> > Christopher, Thx for response, pleas confirm or deny if I
> > understand well.
> >
> > BIO uses thread per http connection (tcp connectio
Christopher, Great Thanks.
BR
Jakub
On Tue, May 24, 2016 at 4:33 AM, Christopher Schultz <
ch...@christopherschultz.net> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Jakub,
>
> On 5/23/16 8:03 PM, Ja kub wrote:
> > Christopher, Thx for response, pleas confirm or deny if I
> > un
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jakub,
On 5/23/16 8:03 PM, Ja kub wrote:
> Christopher, Thx for response, pleas confirm or deny if I
> understand well.
>
> BIO uses thread per http connection (tcp connection). (Shame I
> didn't realize it!) NIO uses thread per request.
It's more
Christopher,
Thx for response, pleas confirm or deny if I understand well.
BIO uses thread per http connection (tcp connection). (Shame I didn't
realize it!)
NIO uses thread per request.
With NIO thread is returned to pool as soon as request is finished (doGet
ends).
With BIO thread is returned t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jakub,
On 5/23/16 11:38 AM, Ja kub wrote:
> In which scenario nio connector will outerform basic io connector
> and vice versa ?
In Tomcat 8.5 and higher, NIO will always outperform the BIO connector
because the BIO connector has been completely re
>
>
> Collecting some peak usage data might be interesting. You definitely want
> your max thread limit to be a bit above the number of concurrent requests
> you're handling. Of course, that has to be balanced against limits on
> other resources, such as memory and data base connections.
>
> - C
> From: John Smith [mailto:tomcat.ran...@gmail.com]
> Subject: Re: NIO connector - connections and threads
> If you're implying are 200 people simultaneously, hitting the same page at
> the same time, or making the same HTTP POST at the same time, the answer
> is, yes, probab
On Mon, Mar 10, 2014 at 11:48 AM, Caldarale, Charles R <
chuck.caldar...@unisys.com> wrote:
> > From: John Smith [mailto:tomcat.ran...@gmail.com]
> > Subject: Re: NIO connector - connections and threads
>
> Don't top post.
>
> > So are the open HTTP connec
> From: John Smith [mailto:tomcat.ran...@gmail.com]
> Subject: Re: NIO connector - connections and threads
Don't top post.
> So are the open HTTP connections that use my web application code waiting
> in line to be processed by the available threads specified in maxThreads?
Thanks for your reply. So are the open HTTP connections that use my web
application code waiting in line to be processed by the available threads
specified in maxThreads?
Best,
John
On Sun, Mar 9, 2014 at 12:44 PM, Konstantin Kolinko
wrote:
> 2014-03-09 2:08 GMT+04:00 John Smith :
> > Sorry, fo
2014-03-09 2:08 GMT+04:00 John Smith :
> Sorry, forgot: Tomcat 7.0.42
>
>
> On Fri, Mar 7, 2014 at 3:59 PM, John Smith wrote:
>
>> The NIO connector has two attributes from the standard HTTP Connector
>> implementation, maxConnections and maxThreads with defaults of 1 and
>> 200, respectively.
Sorry, forgot: Tomcat 7.0.42
On Fri, Mar 7, 2014 at 3:59 PM, John Smith wrote:
> The NIO connector has two attributes from the standard HTTP Connector
> implementation, maxConnections and maxThreads with defaults of 1 and
> 200, respectively.
>
> Can anyone shine some light on how these wor
to:icici...@gmail.com]
> Sent: Tuesday, January 15, 2013 5:19 PM
> To: Tomcat Users List
> Subject: Re: NIO connector issue: SEVERE: Error processing request
>
> On Wed, Jan 16, 2013 at 9:34 AM, Kevin Priebe >wrote:
>
> > Hi,
> >
> >
> >
> > We have a
and will gather a
bunch of more info as Igor and Chris suggested.
Kevin
-Original Message-
From: Igor Cicimov [mailto:icici...@gmail.com]
Sent: Tuesday, January 15, 2013 5:19 PM
To: Tomcat Users List
Subject: Re: NIO connector issue: SEVERE: Error processing request
On Wed, Jan 16,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Kevin,
On 1/15/13 5:34 PM, Kevin Priebe wrote:
> We have a setup with Nginx load balancing between 2 clustered
> tomcat instances. 1 instance is on the same server as Nginx and
> the other is on a separate physical server (same rackspace). We’re
>
On Wed, Jan 16, 2013 at 9:34 AM, Kevin Priebe wrote:
> Hi,
>
>
>
> We have a setup with Nginx load balancing between 2 clustered tomcat
> instances. 1 instance is on the same server as Nginx and the other is on a
> separate physical server (same rackspace). We’re using pretty standard
> default
Christopher,
Thanks for the help. I will log this in Bugzilla shortly.
-parag
-Original Message-
From: Christopher Schultz [mailto:ch...@christopherschultz.net]
Sent: Saturday, February 05, 2011 4:06 AM
To: Tomcat Users List
Subject: Re: Nio Connector and self signed SSL certificate
.
Regards,
Parag
-Original Message-
From: Brett Delle Grazie [mailto:brett.dellegra...@gmail.com]
Sent: Saturday, February 05, 2011 1:30 PM
To: Tomcat Users List
Subject: Re: Nio Connector and self signed SSL certificate giving "No client
certificate chain in this request"
Hi,
On 4 February 2011 22:36, Christopher Schultz
wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Parag,
>
> On 2/4/2011 5:04 AM, Parag Thakur wrote:
>
>> When I try to access a secure URL (e.g. /secure/foo.do) from a java
>> program using apache httpclient library (where the client
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Parag,
On 2/4/2011 5:04 AM, Parag Thakur wrote:
> When I try to access a secure URL (e.g. /secure/foo.do) from a java
> program using apache httpclient library (where the client is configured
> to use "C:\keys\webserver.keystore" as the truststore an
Thanks. So is this behavior due to SSL renegotiation?
Also, would the ciphers issue be related to this?
Thanks again,
Parag
-Original Message-
From: Mark Thomas [mailto:ma...@apache.org]
Sent: Friday, February 04, 2011 3:38 PM
To: Tomcat Users List
Subject: Re: Nio Connector and self
On 04/02/2011 10:04, Parag Thakur wrote:
> Oddly, the same program works if I use
> org.apache.coyote.http11.Http11Protocol instead of
> org.apache.coyote.http11.Http11NioProtocol. Any idea what might be
> causing the NIO implementation to not work in this case? Does this have
> anything to do with
Hi Mark,
Since I have registered today to the users@tomcat.apache.org I was not sure
if my registration has been successful. So I was confused if my
question has made it to the list and that is the reason I have re-posted it.
Thanks
Ashish
On Fri, Mar 5, 2010 at 7:01 PM, Mark Thomas wrote:
>
On 05/03/2010 13:25, Ashish Jain wrote:
> On Fri, Mar 5, 2010 at 8:35 AM, Ashish Jain wrote:
>
>> Hi,
>>
>> I am having an application which is based on comet and dojo. The
>> application uses ActiveMQ to publish messages.I am using firebug to see the
>> request/response of the XMLHttprrequests.
On Fri, Mar 5, 2010 at 8:35 AM, Ashish Jain wrote:
> Hi,
>
> I am having an application which is based on comet and dojo. The
> application uses ActiveMQ to publish messages.I am using firebug to see the
> request/response of the XMLHttprrequests. I see a difference in behaviour in
> tomcat 6.0.1
toClient.close();
} catch (Exception e) {
System.err.println("Exception in doGet: "+e.toString());
} finally {
servedThreads--;
}
}
}
-Original Message-
From: Filip Hanik - Dev Lists [mailto:devli...@hanik.com]
Sent: den 13 januari 2010 18:46
To:
essage-
From: Filip Hanik - Dev Lists [mailto:devli...@hanik.com]
Sent: den 13 januari 2010 16:13
To: Tomcat Users List
Subject: Re: NIO-connector problems (excessive CPU-usage)
yes, the issue is known. However, we have not been able to create a use
case for it, since I've never been
at java.lang.Thread.run(Thread.java:619)
/Tobias
-Original Message-
From: Filip Hanik - Dev Lists [mailto:devli...@hanik.com]
Sent: den 13 januari 2010 16:13
To: Tomcat Users List
Subject: Re: NIO-connector problems (excessive CPU-usage)
yes, the issue is known. However, we have not b
yes, the issue is known. However, we have not been able to create a use
case for it, since I've never been able to reproduce it.
One of the work arounds would be to close the selector, but that is a
royal pain, since you'd then have to reregister all keys and you'd end
up in a synchronization ni
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Filip,
On 5/27/2009 10:03 AM, Filip Hanik - Dev Lists wrote:
> the warning would only print when a GC happens and there are some keys
> that haven't been cancelled but dereferenced.
> I will work on this, but it should not cause any problems since the
Thanks Chris,
the warning would only print when a GC happens and there are some keys
that haven't been cancelled but dereferenced.
I will work on this, but it should not cause any problems since the keys
will be cleaned out.
Filip
Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Filip,
On 5/27/2009 8:45 AM, Filip Hanik - Dev Lists wrote:
> Christopher Schultz wrote:
>>
>> These are the warnings I received:
>>
>> May 23, 2009 5:03:20 AM
>> org.apache.tomcat.util.net.NioBlockingSelector$KeyReference finalize
>> WARNING: Possib
Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
All,
(I have no idea why my messages are getting messed-up... apologies for
the empty messages... I swear I'm sending whole messages!)
During performance testing, I got the following warnings in
catalina.out. I'm using th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
André,
On 5/26/2009 12:32 PM, André Warnier wrote:
> Christopher Schultz wrote:
> ...
> Your last one about "Apache vs Tomcat.." (including NIO results) got
> there fine.
> But the last couple which you sent on "NIO connector:" appear empty,
> apart f
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
All,
(I have no idea why my messages are getting messed-up... apologies for
the empty messages... I swear I'm sending whole messages!)
During performance testing, I got the following warnings in
catalina.out. I'm using the NIO connector (along with t
Christopher Schultz wrote:
...
Your last one about "Apache vs Tomcat.." (including NIO results) got
there fine.
But the last couple which you sent on "NIO connector:" appear empty,
apart from an attachment that just says "Version 1".
Anyway, that's how I saw them.
-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
André,
On 5/24/2009 6:19 AM, André Warnier wrote:
> Christopher Schultz wrote:
>
> Although fresh from the tree, my lemon juice doesn't work, neither does
> the sun of Spain as heat source.
> Chris, you may be posting stuff, but it doesn't get here.
Christopher Schultz wrote:
Although fresh from the tree, my lemon juice doesn't work, neither does
the sun of Spain as heat source.
Chris, you may be posting stuff, but it doesn't get here.
-
To unsubscribe, e-mail: users-unsu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Filip,
On 5/22/2009 10:14 AM, Filip Hanik - Dev Lists wrote:
> [The NIO connector in 6.0.18] simply never called close on the FD when it was
> done
I tried the tomcat-coyote.jar from Tomcat 6.0.20 and everything worked
quite well. Thanks a lot for c
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Rainer,
On 5/22/2009 8:48 AM, Rainer Jung wrote:
> The file descriptos thing is totaly independent. I hijacked the thread :)
Yeah, I know. Filip independently mentioned that there's a fd leak in
the NIO implementation includes in 6.0.18. I have yet t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Rainer,
On 5/22/2009 10:32 AM, Rainer Jung wrote:
> On 22.05.2009 15:46, Christopher Schultz wrote:
>> Rainer,
>>
>> On 5/22/2009 8:55 AM, Rainer Jung wrote:
>>> You could run a JSP including a call to System.gc();
>> Right. The JVM is out of file des
Filip,
On 5/22/2009 10:14 AM, Filip Hanik - Dev Lists wrote:
> if you look at the commit, there are changelog changes in there. one of
> them being a FD leak with static content.
Gotcha. I was just looking at the commit comment itself.
> It simply never called close on the FD when it was done
O
On 22.05.2009 15:46, Christopher Schultz wrote:
> Rainer,
>
> On 5/22/2009 8:55 AM, Rainer Jung wrote:
>> You could run a JSP including a call to System.gc();
>
> Right. The JVM is out of file descriptors. I cannot deploy a new JSP
> onto the server without restarting it. ;) I mentioned this in m
Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Filip,
On 5/21/2009 12:34 PM, Filip Hanik - Dev Lists wrote:
hi Christopher, generally, ulimit -n 1024 is too low for any kind of web
server.
Fair enough, but I'm not putting an unreasonable load on my server wi
Rainer,
On 5/22/2009 8:55 AM, Rainer Jung wrote:
> You could run a JSP including a call to System.gc();
Right. The JVM is out of file descriptors. I cannot deploy a new JSP
onto the server without restarting it. ;) I mentioned this in my initial
post.
> First of all this really looks bad and int
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Filip,
On 5/21/2009 12:34 PM, Filip Hanik - Dev Lists wrote:
> hi Christopher, generally, ulimit -n 1024 is too low for any kind of web
> server.
Fair enough, but I'm not putting an unreasonable load on my server with
ulimit -n 1024 and 40 concurrent
Hi Chris,
On 22.05.2009 14:29, Christopher Schultz wrote:
>>> $ jmap -heap 1430
>>> Attaching to process ID 1430, please wait...
>>> Debugger attached successfully.
>>> Client compiler detected.
>>> JVM version is 11.3-b02
>>>
>>> using thread-local object allocation.
>>> Mark Sweep Compact GC
>>>
Hi Chris,
On 22.05.2009 14:14, Christopher Schultz wrote:
> Rainer,
>
> On 5/21/2009 12:21 PM, Rainer Jung wrote:
>> 2 remarks about all your stress testing efforts:
>
>> A) TIME_WAIT
>
>> When not doing HTTP Keep-Alive, under high load the size of the TCP hash
>> table and the effectiveness of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Rainer,
On 5/21/2009 12:13 PM, Rainer Jung wrote:
> On 21.05.2009 17:55, Christopher Schultz wrote:
>> All,
>>
>> I've been testing the performance of various Tomcat configurations
>> against Apache httpd and my serious tests are not completing for th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Rainer,
On 5/21/2009 12:21 PM, Rainer Jung wrote:
> 2 remarks about all your stress testing efforts:
>
> A) TIME_WAIT
>
> When not doing HTTP Keep-Alive, under high load the size of the TCP hash
> table and the effectiveness of the system to lookp u
hi Christopher, generally, ulimit -n 1024 is too low for any kind of web
server.
And there was also a file descriptor leak in the NIO connector, fixed in
http://svn.apache.org/viewvc?rev=734454&view=rev
this is when Tomcat NIO serves up static content.
Filip
Christopher Schultz wrote:
-B
2 remarks about all your stress testing efforts:
A) TIME_WAIT
When not doing HTTP Keep-Alive, under high load the size of the TCP hash
table and the effectiveness of the system to lookp up TCP connections
can limit the throughput you can reach. More precisely, depending on the
excat way of connec
On 21.05.2009 17:55, Christopher Schultz wrote:
> All,
>
> I've been testing the performance of various Tomcat configurations
> against Apache httpd and my serious tests are not completing for the NIO
> connector because the server is running out of files:
>
>> May 20, 2009 2:35:55 AM org.apache.
otismo wrote:
Thanks for checking it out, Filip.
I'm running this on what will be 6.0.19, meaning 6.0.x/trunk
Yes, running from the trunk yields very different #s. Looking into it more,
6.0.18 didn't honor the pollerThreadCount setting.
results (all tests were run for around 3000 sa
Thanks for checking it out, Filip.
> I'm running this on what will be 6.0.19, meaning 6.0.x/trunk
Yes, running from the trunk yields very different #s. Looking into it more,
6.0.18 didn't honor the pollerThreadCount setting.
results (all tests were run for around 3000 samples):
6.0.18:
with 2
hi Peter,
I ran your jmeter test and I get an average request time for Comet to be
13.5 seconds.
I'm running this on what will be 6.0.19, meaning 6.0.x/trunk
With a 10second timeout, you wont get timed out in exactly 10 seconds.
timeout are of absolutely lowest priority.
If there is request data
Thanks for the response, Filip. Hopefully this is more helpful...
I put a war at http://www.nomad.org/test.war containing my web app, the
source, and my jmeter test plan.
My question: why are comet timeouts getting generated substantially behind
the timeout setting?
Is it because I have incorr
peter, if you post your test code packaged in such a way that who ever
helps you doesn't have to reverse engineer your app to setup the test
case and test it locally, then you most likely wont have to pay anyone
to help you.
The more effort you provide in providing information to the list,
incl
Sorry to bump this thread. I'm willing to pay for some assistance if
anyone's interested in helping. I'm trying to figure out 2 problems
when running my system under a light-moderate load test:
1) why do my comet timeout events not get generated on time (supposed
to be every 50 seconds, averagin
I'm trying to figure out how best to configure nio so that my comet
timeout events get generated in a timely manner. I have the comet
events set to generate a timeout every 50 seconds. Works fine with
few users. Under a moderate but reasonable load the timeout gets
generated on average every 113
Thanks for the tips. Very helpful.
>> I also get the warning when trying to use keepAliveTimeout.
>> Is this property available for the nio connector?
>
> No; it's only listed under the older connector (the one labeled "Standard
> Implementation" that then somewhat ambiguously refers to HTTP).
> From: Peter Warren [mailto:tomcat.subscript...@gmail.com]
> Subject: nio connector configuration
I can't answer your real questions, but here's a bit for your minor ones.
> the acceptorThreadPriority and pollerThreadPriority are
> set using ints because I get the following warnings in the
> cat
Hmm, I just tried converting the keystore to JKS (using
org.mortbay.util.PKCS12Import) and that worked. So the JKS keystore seems
to work fine with the NIO connector, but the PKCS12 keystore only works with
non-NIO.
On 9/11/08, Tim McCune <[EMAIL PROTECTED]> wrote:
>
> I've been using the NIO con
it's in the "java" directory of the zip file
Filip
neil davudo wrote:
Where?
I downloaded the entire Tomcat source code. Can you point me to the
directories?
TIA
Neil
markt-2 wrote:
neil davudo wrote:
Where can I find the source code for the NIO connector that uses the
CometProces
neil davudo wrote:
Where?
I downloaded the entire Tomcat source code. Can you point me to the
directories?
Did you even try searching for files with nio in the name? I really don't
see why you expect me to do this for you.
Mark
-
tomcat.apache.org, click download link, there is a zip file containing
the source.
Filip
neil davudo wrote:
Where?
I downloaded the entire Tomcat source code. Can you point me to the
directories?
TIA
Neil
markt-2 wrote:
neil davudo wrote:
Where can I find the source code for the
Where?
I downloaded the entire Tomcat source code. Can you point me to the
directories?
TIA
Neil
markt-2 wrote:
>
> neil davudo wrote:
>> Where can I find the source code for the NIO connector that uses the
>> CometProcessor?
>
> http://tomcat.apache.org
>
> Mark
>
> --
later this will be resolved.
Regards,
-Emile
-Original Message-
From: Filip Hanik - Dev Lists [mailto:[EMAIL PROTECTED]
Sent: Monday, February 25, 2008 5:57 PM
To: Tomcat Users List
Subject: Re: NIO connector under heavy load drops incoming requests?
you don't need four (4) accept
Alan Chaney wrote:
Actually I've seen something like this. I'm under a lot of pressure to
get something out so I haven't investigated it further, but what seemed
to be happening is that if the client slowed down the NIO connector was
throwing a SocketTimeout. I tried messing about with the timeo
you don't need four (4) acceptor threads, turn that to one (1)
also, you omited the most interesting stack trace :)
Filip
Emile Litvak wrote:
Hello everyone,
We have a high load environment where we are running tomcat 5.5.15
successfully. We are interesting in reducing the system CPU load
Actually I've seen something like this. I'm under a lot of pressure to
get something out so I haven't investigated it further, but what seemed
to be happening is that if the client slowed down the NIO connector was
throwing a SocketTimeout. I tried messing about with the timeout
settings but cou
there is a working Bayeux example, that also shows that Comet works, a
little more icing on the cake than necessary
steps to get it
1. check out the code from SVN
svn co --username tomcat --password tomcat
http://svn.hanik.com/svn/repos/tomcat-bayeux
2. Copy the application
a) copy tomcat-bay
On Thu, Oct 25, 2007 at 12:19 PM, Filip Hanik - Dev Lists wrote:
> browser don't work the way you might it expect to, firefox for example,
> will not display anything until the entire request is complete. so the
> chat example is no good that way.
> write a client application for your comet, to
neil davudo wrote:
Where can I find the source code for the NIO connector that uses the
CometProcessor?
http://tomcat.apache.org
Mark
-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROT
Rockin. I'll check it out when it's released. Thanks
On Feb 1, 2008 7:17 AM, Filip Hanik - Dev Lists <[EMAIL PROTECTED]> wrote:
> 6.0.16 will have this fixed I believe
>
>
> Filip
>
> brien colwell wrote:
> > hi Filip,
> >
> > Still no success there ... I think I'm missing something fundamental.
>
6.0.16 will have this fixed I believe
Filip
brien colwell wrote:
hi Filip,
Still no success there ... I think I'm missing something fundamental.
Just in case anyone is interested, I'm running Tomcat 6.0.13, JDK
1.6.0_04, with libnative for the APR connector. I'm going to stick to
APR for now .
PROTECTED]
Sent: Friday, February 01, 2008 6:45 AM
To: Tomcat Users List
Subject: Re: NIO connector
hi Filip,
Still no success there ... I think I'm missing something fundamental.
Just in case anyone is interested, I'm running Tomcat 6.0.13, JDK
1.6.0_04, with libnative for the APR con
hi Filip,
Still no success there ... I think I'm missing something fundamental.
Just in case anyone is interested, I'm running Tomcat 6.0.13, JDK
1.6.0_04, with libnative for the APR connector. I'm going to stick to
APR for now ... I wanted to run a benchmark, but it's not critical.
Best regards,
Connector c =
e.createConnector((String)null,8080,"org.apache.coyote.http11.Http11NioProtocol");
Filip
brien colwell wrote:
hi Filip,
Thanks for the tip. Any thoughts on why createConnector would give null?
embedded.createConnector( (InetAddress) null, port,
"
hi Filip,
Thanks for the tip. Any thoughts on why createConnector would give null?
embedded.createConnector( (InetAddress) null, port,
"org.apache.coyote.http11.Http11NioProtocol" );
Brien
On Jan 31, 2008 7:15 AM, Filip Hanik - Dev Lists <[EMAIL PROTECTED]> wro
use
public Connector createConnector(String address, int port,String protocol)
set org.apache.coyote.http11.Http11NioProtocol as the protocol value
should work
Filip
brien colwell wrote:
hi all --
I'm trying to hook the NIO connector to an engine, but I'm lost in how
to do this. I'm using To
browser don't work the way you might it expect to, firefox for example,
will not display anything until the entire request is complete. so the
chat example is no good that way.
write a client application for your comet, to test how it works
Filip
javaxmlsoapdev wrote:
I am trying to use NIO co
83 matches
Mail list logo
