Re: [Web-SIG] Last call for WSGI 1.0 errata/clarifications

2010-09-24 Thread Jeff Hardy
On Thu, Sep 23, 2010 at 10:32 AM, P.J. Eby wrote: > Just a reminder: I'm planning to actually update PEP 333 over the weekend > and start working on wsgiref updates, so if you have any last-minute > comments on the proposal, now's the time to post them, however unpolished > they may be! Will you

Re: [Web-SIG] Output header encodings? (was Re: Backup plan: WSGI 1 Addenda and wsgiref update for Py3)

2010-09-23 Thread Jeff Hardy
On Thu, Sep 23, 2010 at 11:52 AM, P.J. Eby wrote: >> I do think input and output should be symmetric, though. If response >> headers are going to be bytes, then the request headers should be as >> well, or vice versa. The same arguments apply to both, after all. > > Actually, they don't.  There ar

Re: [Web-SIG] Output header encodings? (was Re: Backup plan: WSGI 1 Addenda and wsgiref update for Py3)

2010-09-23 Thread Jeff Hardy
On Thu, Sep 23, 2010 at 10:06 AM, P.J. Eby wrote: > So, unless somebody has some additional arguments on this one, I think I'm > going to stick with bytes output. I don't have a strong opinion on whether it should be bytes or strings -- I'll leave that discussion for people who know more about th

Re: [Web-SIG] [Python-Dev] Backup plan: WSGI 1 Addenda and wsgiref update for Py3

2010-09-21 Thread Jeff Hardy
On Tue, Sep 21, 2010 at 10:57 AM, Ian Bicking wrote: > On Tue, Sep 21, 2010 at 12:09 PM, P.J. Eby wrote: >> >> The Python 3 specific changes are to use: >> >> * ``bytes`` for I/O streams in both directions >> * ``str`` for environ keys and values >> * ``bytes`` for arguments to start_response() a

Re: [Web-SIG] [Python-Dev] Backup plan: WSGI 1 Addenda and wsgiref update for Py3

2010-09-21 Thread Jeff Hardy
On Tue, Sep 21, 2010 at 10:47 AM, Chris McDonough wrote: > On Tue, 2010-09-21 at 12:09 -0400, P.J. Eby wrote: > If a WSGI-1-compatible protocol seems more sensible to folks, I'm > personally happy to defer discussion on PEP 444 or any other > backwards-incompatible proposal. I think both make sen

[Web-SIG] NWSGI 1.0 Released

2008-12-27 Thread Jeff Hardy
I'm very pleased to announce the release of NWSGI 1.0. NWSGI is an implementation of the WSGI specification (PEP 333) for IronPython. It is implemented as an ASP.NET HttpHandler and is supported on IIS 6 and IIS 7 (and should work on any other ASP.NET-capable web server). NWSGI allows the integrati

[Web-SIG] NWSGI 0.7 released

2008-12-04 Thread Jeff Hardy
NWSGI 0.7 is now available. This version adds support for ASP.NET sessions, fixes Unicode handling, and adds support for wildcard mappings. It is available at http://www.codeplex.com/NWSGI/Release/ProjectReleases.aspx?ReleaseId=20189. What is NWSGI? NWSGI is an ASP.NET HttpHandler that implements