Re: [Web-SIG] WSGI for Python 3

makes porting Python 2 applications easy or even completely transparent (from a WSGI spec point of view). Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter" ___ Web-SIG mailing list Web-SIG@python.o

Re: [Web-SIG] Removal of Cookie in Python 3.0 OK?

that this is going to lead to a high-quality product. > > I'd much rather see language developers put some focus on making a low- > level feature like a packaging system work as well as possible. Amen to that. :-) Regards, Stephan -- Stephan Richter We

Re: [Web-SIG] Logging the authenticated user (was Re: Bowing out)

thoughts? This sounds really good! Thanks for the great summary and suggestions. As far as I can tell it solves all of our use cases and addresses our security concerns; i.e. not sending the username to the client. Regards, Stephan -- Stephan Richter CBU

Re: [Web-SIG] Bowing out (was Re: A trivial template API counter-proposal)

ll, that the egg work is more important. :-) BTW, did we reach a conclusion on the user logging issue. We really, really need to solve that somehow. Anything you can come up with is fine by me; I'll trust you do the right thing. Regards, Stephan -- Stephan Richter CBU Physics & Che

Re: [Web-SIG] WSGI in standard library

On Saturday 04 February 2006 21:35, Peter Hunt wrote: > I think CherryPy's WSGI server should go in: it's stable, and the > best-performing WSGI HTTP server out there. Are you sure? Is it really scalable? Can you prove it? Regards, Stephan -- Stephan Richter CBU Physics

Re: [Web-SIG] Communicating authenticated user information

On Monday 23 January 2006 22:15, Clark C. Evans wrote: > On Mon, Jan 23, 2006 at 04:15:06PM -0500, Phillip J. Eby wrote: > | At 03:36 PM 1/23/2006 -0500, Stephan Richter wrote: > | > Specify a new environment variable called 'wsgi.user' (or something > | > similar)

Re: [Web-SIG] Communicating authenticated user information

the application handle the encoding. Regards, Stephan -- Stephan Richter CBU Physics & Chemistry (B.S.) / Tufts Physics (Ph.D. student) Web2k - Web Software Design, Development and Training ___ Web-SIG mailing list Web-SIG@python.org Web SIG: http

Re: [Web-SIG] Communicating authenticated user information

something like that it should say. Of course, one could argue that you possibly want to send other information for logging to the server, but I would call this YAGNI. Regards, Stephan -- Stephan Richter CBU Physics & Chemistry (B.S.) / Tufts Physics (Ph.D. student) Web2k - Web Software

Re: [Web-SIG] Communicating authenticated user information

allows outer middleware to override what inner middleware or the > application set it to. +1. If we would have this in the specs, I would be totally happy. Regards, Stephan -- Stephan Richter CBU Physics & Chemistry (B.S.) / Tufts Physics (Ph.D. student) Web2k - Web Software Design, Devel

Re: [Web-SIG] Communicating authenticated user information

eally a viable solution either, since it defeats the point of a non-specific API, like WSGI. We thought about the problem quiet a bit and decided that the user is really the only thing that the log really has to know from the application. So a simple callback that expects a simple string would be