And make it a (low-level but) true Request object. We're not looking for "one true request," but rather, "requests all the way down." The WSGI NG request object should be pretty basic, and should be designed to support an ecosystem of more advanced request objects at the framework layer.
For comparison, consider Node: they have a core IncomingMessage prototype that gets passed to http.Server callbacks as request, and then frameworks wrap that in their own request or req objects: Express, Sails (wraps Express, actually), Total, Koa. Fundamentally, though, every framework is using the same request object at bottom.
In a sense WSGI's environ has been our base request object. Let's start calling it that, and design it as such.
And make it a (low-level but) true
Requestobject. We're not looking for "one true request," but rather, "requests all the way down." The WSGI NG request object should be pretty basic, and should be designed to support an ecosystem of more advanced request objects at the framework layer.For comparison, consider Node: they have a core IncomingMessage prototype that gets passed to
http.Servercallbacks asrequest, and then frameworks wrap that in their ownrequestorreqobjects: Express, Sails (wraps Express, actually), Total, Koa. Fundamentally, though, every framework is using the same request object at bottom.In a sense WSGI's
environhas been our baserequestobject. Let's start calling it that, and design it as such.Reticketed from #13.