No, I accidentally only replied to you first because I click on the wrong reply link in gmail :) As for WAI, you could be correct. On Tue, Feb 1, 2011 at 5:17 PM, Aristid Breitkreuz wrote:

Did I accidentally reply just to you? Sorry, I was expecting better default behavior of Gmail... After a closer look, I now see that WAI really is mostly just types, but those types DO seem to be fairly server-centric. Response especially does not seem to be particularly useful for clients, but Request might need some modifications too.

Aristid

2011/2/2 Jeremy Shaw

...

I am not sure what you mean. WAI does not actually include a server. It is just the Request/Response types, status codes, and some headers,

http://hackage.haskell.org/packages/archive/wai/0.3.1/doc/html/Network-Wai.h...

if you want an actual server (which you don't) then you would need warp or something.

- jeremy

On Tue, Feb 1, 2011 at 4:59 PM, Aristid Breitkreuz wrote:

...

WAI is too wide in scope, IMO. I would like to be able to use http-types in client-only code that does not want any of the HTTP server functionality.

Aristid

2011/2/1 Jeremy Shaw

...

This is essentially what WAI is supposed to be. (Though WAI is more server focused).

I think it is a good idea, but people seem unhappy to standardize on what those types should look like...

- jeremy

On Tue, Feb 1, 2011 at 1:55 PM, Aristid Breitkreuz wrote:

...

Hi, Hear me out, I have an idea! :-) How about creating a new package "http-types" containing Request / Response / status code / header name types for HTTP. These could be used by both server and client software, and might even allow switching between HTTP client libraries (say, if I want to switch between http-enumerator and HTTP). What do you think?

Aristid _______________________________________________ web-devel mailing list web-devel@haskell.org http://www.haskell.org/mailman/listinfo/web-devel