Where Rev could be going...

[Sivakatirswami]

> 
> On 18 Nov 2006, at 20:19, Dan Shafer wrote:
Each execution
>> of the
>> CGI is effectively blocking in nature. (I'm over-simplifying a bit 
>> here, I
>> know, but I think this is the primary concern in broad terms.) 

Dave Cragg wrote:

Dan,  I don't think this is correct.
> 
> Each call to a Rev CGI on a server will start a new instance of the Rev 
> engine. Many instances can be running at the same time, and whichever 
> completes first will return first.
> 
> I just tested this with two CGI scripts to make sure. One CGI was timed 
> to take 5 seconds to complete. The second was timed to take 1 second. I 
> called the long one first, and then the short one. The short one 
> returned first.
> 
> To test this from Rev on the client side is a bit tricky. You need to 
> run two instances of Rev, one for each CGI. This is because if you use 
> Rev's load url command to two urls from the same server, the second load 
> request won't be issued from the client until the first has completed. 
> Is it possible that the client behavior was giving you a misleading 
> picture of the server behavior?
> 
> Cheers
> Dave

Would this be a good test?

1) create 5 tasks that run from 5 different CGI
2) Each one returns some HTML chunk
3) Embed these in a single web page as SSI exec requests,
load the page... see what happens

We currently have this one:

<!--#exec cgi="/cgi-bin/local_nav_include.cgi" -->

on *every* page on the www.himalayanacademy.com site.

but, JBV's testimony seems good enough for me, that was 2002
this is 2006 with dual XEON processors on our box.