In my ongoing attempts to pull Paste apart into more pieces, I've extracted the functionality of paste.wsgiwrappers.WSGIRequest and paste.request into a separate package called wsgireq. It's just in svn now, I'm not sure exactly what I'll do with it. Maybe deprecate the current Paste functions, and have them forward to functions in wsgireq. But not for a while.
I'd like feedback on the API. It's mostly like WSGIRequest, though without some stuff like defaults that I found weird. I'd rather have projects subclass the object if they want to change the defaults, or just instantiate it the way they want. It can take an environ getter function instead of just a concrete environ, so you can instantiate it once per project and point it at a function that does a threadlocal get, if you'd like. I did change GET and POST to queryvars and postvars, because I didn't really like the GET/POST names: GET is always set, for instance, because all requests can have query strings, and POST only returns values for wwwurlencoded values, not any POST body. But maybe that's too much of an API change. Certainly at least a deprecation warning would be proper. Most other stuff hasn't changed. I would like to include parsing of all typical request headers. In this way it also replaces parts of paste.httpheaders. The number of headers that are meaningful for the request is relatively small. I've also included a few more handy URL-related methods, req.read_body() to read the body of the request, and a modest attempt and not stealing wsgi.input from other consumers. -- Ian Bicking : [EMAIL PROTECTED] : http://blog.ianbicking.org : Write code, do good : http://topp.openplans.org/careers _______________________________________________ Paste-users mailing list [email protected] http://webwareforpython.org/cgi-bin/mailman/listinfo/paste-users
