Did I accidentally reply just to you? Sorry, I was expecting better default behavior of Gmail...<div><br></div><div>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.</div>
<div><br></div><div><br></div><div>Aristid</div><div><br><br><div class="gmail_quote">2011/2/2 Jeremy Shaw <span dir="ltr"><<a href="mailto:jeremy@n-heptane.com">jeremy@n-heptane.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
I am not sure what you mean. WAI does not actually include a server.<br>
It is just the Request/Response types, status codes, and some headers,<br>
<br>
<a href="http://hackage.haskell.org/packages/archive/wai/0.3.1/doc/html/Network-Wai.html" target="_blank">http://hackage.haskell.org/packages/archive/wai/0.3.1/doc/html/Network-Wai.html</a><br>
<br>
if you want an actual server (which you don't) then you would need<br>
warp or something.<br>
<br>
- jeremy<br>
<br>
On Tue, Feb 1, 2011 at 4:59 PM, Aristid Breitkreuz<br>
<div><div></div><div class="h5"><<a href="mailto:aristidb@googlemail.com">aristidb@googlemail.com</a>> wrote:<br>
> WAI is too wide in scope, IMO. I would like to be able to use http-types in<br>
> client-only code that does not want any of the HTTP server functionality.<br>
><br>
> Aristid<br>
><br>
> 2011/2/1 Jeremy Shaw <<a href="mailto:jeremy@n-heptane.com">jeremy@n-heptane.com</a>><br>
>><br>
>> This is essentially what WAI is supposed to be. (Though WAI is more<br>
>> server focused).<br>
>><br>
>> I think it is a good idea, but people seem unhappy to standardize on<br>
>> what those types should look like...<br>
>><br>
>> - jeremy<br>
>><br>
>> On Tue, Feb 1, 2011 at 1:55 PM, Aristid Breitkreuz<br>
>> <<a href="mailto:aristidb@googlemail.com">aristidb@googlemail.com</a>> wrote:<br>
>> > Hi,<br>
>> > Hear me out, I have an idea! :-)<br>
>> > How about creating a new package "http-types" containing Request /<br>
>> > Response<br>
>> > / status code / header name types for HTTP. These could be used by both<br>
>> > server and client software, and might even allow switching between HTTP<br>
>> > client libraries (say, if I want to switch between http-enumerator and<br>
>> > HTTP).<br>
>> > What do you think?<br>
>> ><br>
>> > Aristid<br>
>> > _______________________________________________<br>
>> > web-devel mailing list<br>
>> > <a href="mailto:web-devel@haskell.org">web-devel@haskell.org</a><br>
>> > <a href="http://www.haskell.org/mailman/listinfo/web-devel" target="_blank">http://www.haskell.org/mailman/listinfo/web-devel</a><br>
>> ><br>
>> ><br>
><br>
><br>
</div></div></blockquote></div><br></div>