Jeremy Kemper wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> On Dec 8, 2005, at 11:47 PM, James Britt wrote:
> 
>> If I'm understanding this correctly, though, I need not be  concerned 
>> with contention issues any more than I would with a plain  CGI app; 
>> fastcgi and scgi are means of routing requests to  persistent CGI 
>> processes, but a given process will not be handling  more than one 
>> request at a time.
> 
> 
> Most FastCGI implementations work this way, but it is not a rule.
> 
> You are free to write a FastCGI server which handles concurrent
> requests (with threads, async IO, forked children, etc.)
> 
> But most do not; programming in the CGI style is much simpler.
> The choice is yours.

I'm writing and deploying Rails and Nitro apps and using fastcgi/scgi at 
different times, and have yet to see any discussion of threading in 
relation to these.  So my belief is that the fcgi and scgi code used in 
such cases is not doing anything that puts conventional CGI-style code 
at risk.

But I was curious if anyone knew of something to the contrary.


James
-- 

http://www.ruby-doc.org       - Ruby Help & Documentation
http://www.artima.com/rubycs/ - Ruby Code & Style: Writers wanted
http://www.rubystuff.com      - The Ruby Store for Ruby Stuff
http://www.jamesbritt.com     - Playing with Better Toys
http://www.30secondrule.com   - Building Better Tools