On Mar 9, 2006, at 5:34 PM, Ian Bicking wrote:
WSGI is an in-process protocol, SCGI is really only an interprocess protocol.
Well I guess SCGI really doesn't care whether it is in-process or not, but I
see what you are saying.
So with WSGI you can compose applications inside a single process, wrap applications (e.g., impose a transaction boundary or catch exceptions), run tests in a simulated environment, or even do the URL traversal as a series of WSGI requests.
This seems to boil down to the variations of the first point, that you can compose applications, in-process, using WSGI. I'm still trying to figure out why I need that.
_______________________________________________ Quixote-users mailing list [email protected] http://mail.mems-exchange.org/mailman/listinfo/quixote-users
