From: Julian Fitzell Date: 2003-01-23T17:55:42+09:00 Subject: Re: mod_ruby: what's persistent and what's shared? Kent Dahl wrote: > Tom Sawyer wrote: > >>On Wednesday 22 January 2003 06:46 pm, Paul DuBois wrote: >> >>>The Apache parent process may spawn a number of children. Suppose the >>>request from USER1 is serviced by child A. If the request from USER2 >>>is also serviced by child A, then it'll be getting the same mod_ruby. >>>If it's serviced by a different child, all bets are off. >>> >>>Moral: You can't rely on the behavior that you appear to want to rely on. >> >>thanks you very much. i understand now. since i did not know for sure i have >>been coding as if this were the case. so all is well. > > > > If you want to be able to rely on globally set variables to be shared > and such, you really want a single Ruby app at the recieving end. That > is, you want IOWA. > > > (Or maybe its just me that wants IOWA very badly after a week of PHP > hacking :-/) > Ugh, try writing IOWA *in* PHP (with a few Seaside-isms thrown in), which is partly what I've been doing contract work on lately. It's actually impressive how well it works considering it's PHP but it's horribly horribly painful all the same. :) Julian -- julian@beta4.com Beta4 Productions (http://www.beta4.com)