Aha! My configuration was on Apache so that's why I wasn't seeing the same
behavior. Good to know the --fork option I always assumed it was forking.
Thanks,
ALI MESDAQ
Sr. Security Researcher
WEBSENSE, INC.
ph: +1.858.320.9466
fax: +1.858.784.4466
www.websense.com
Websense TRITONT
For Essential
Larry,
You're a genius! That was it.
Thanks so much - J
On Tue, Jun 7, 2011 at 4:23 PM, Larry Leszczynski wrote:
> Hi Jeff -
>
>> The problem seems to be a bottleneck in Catalyst, because as soon as
>> the long poll completes all of the waiting status requests complete
>> instantly as well. I had
Hi Jeff -
> The problem seems to be a bottleneck in Catalyst, because as soon as
> the long poll completes all of the waiting status requests complete
> instantly as well. I had imagined that the threading on Catalyst would
> support the functionality I'm looking for.
Just a guess... By any chan
Ali,
Pretty sure - I've run all the network tests and even rolled out
Ethereal to check the packets on the network. I can see the requests
going from the browser to Cat and being stacked up. BTW this works
fine as well, as long as you don't having a pending request. Did your
app use the same long p
Are you sure it's a Catalyst issue? Sounds like it could be a JS issue with
your script waiting for responses before moving on to the rest of the ajax
calls. Are you using any JS frameworks? A good test could be you create a stub
method in catalyst with different wait periods and verify that you
HI,
I am using Catalyst to display some server side data using AJAX.
Essentially there are 3 main blocks:
1) The users browser, runing javascript and using the XMLHttpRequest
object for the AJAX calls
2) The Catalyst web server
3) A remote data server (RDS). This is another Perl app (POE based)
tha
