On Feb 9, 2010, at 10:33 AM, Ross Vandegrift wrote: > Ah crap - I didn't even think of that. That's what I get for > developing on an environment that's different than production! > > Guess I'm stuck putting together a standalone server process to handle > this.
And even if you run the paster serve process, you will need to run multiple ones to fully utilize multi-core machines. On our 8-core servers, I run 8 instances of our application behind nginx proxy. I'm not sure why you need to hold onto these things, but maybe if you do need to, you might want to make your own little internal back-end service, that does nothing but hold these things open, and accepts requests for whatever they provide. That way you can have your N amount of Pylons processes, and they'll all talk to the single instance of your back-end app that holds all these things that can't be pickled. Any details on what exactly you need to hold open? :) Cheers, Ben -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
