I'm interested in serving up my pylons app under Stackless Python - Stackless is more or less single-threaded so the model is somewhat like Twisted but without all the deferreds. Instead of threads, there are tasklets which participate in kind of a cooperative parallelism - as soon as one tasklet blocks, another tasklet is allowed to run until it blocks, and so forth.
Since this is single-threaded, I have some concerns is with these 'global' objects that Pylons provides.. c, h, etc... These are normally thread-local storage right? Does pylons provide any capability to either: - provide a container so I can manage the thread-localness of them (I could store them in a tasklet-local storage) - provide a way to access them from environ rather than as a global? (then I could access them on a per-request basis, independent of what tasklet/thread they're run on) - avoid the use of them entirely? really I'd prefer that these things were just explicit in the request because otherwise it really ties pylons down to a multi-threaded or forked model. Part of the reason I'm using stackless is that I can safely fire off multiple 'parallel' tasklets during a request which makes management of simultaneous database requests dirt-simple. But maybe I'm missing something? Anyone have any ideas here? Alec --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
