On Sun, Jan 11, 2009 at 2:40 PM, Tycon <[email protected]> wrote: > > Does WSGI support remote processes (e.g. on other machines) ? If not > then it's a dead end for scalability. I don't see any reason to use > proprietary protocol when more standard ones exist. I'm only talking > about the spec for daemon mode, not the rest of WSGI call spec.
I don't even know what you're asking. WSGI is a function signature and return value, see PEP 333. It doesn't have a daemon mode or even a server. PasteHTTPServer is a simple multithreaded server, and that's why it's the default. It's not meant to be a high-end server for the most demanding tasks. You can write your own server if you don't approve of any of the existing ones. The WSGI environ dict can be pickled and sent via RPC (assuming you use StringIO objects rather than real file handles). But you can't pickle a function or iterator, so you can't wholly do WSGI over RPC. But that's not its purpose. There are other protocols such as SCGI and HTTP for talking to other computers. WSGI is intended for in-process chaining of chunks of Python code that may have been written by different people. -- Mike Orr <[email protected]> --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
