http-enumerator could at least for compatibility support a Request type with ByteString. And also a native request type. Or something along these lines.<div><br></div><div>The problem is that I want to be able to use a Request type that is compatible between multiple client libraries, enabling me to theoretically switch implementations without a huge amount of hassle.<br>
<div><br></div><div>Aristid<br><br><div class="gmail_quote">2011/2/2 Michael Snoyman <span dir="ltr"><<a href="mailto:michael@snoyman.com">michael@snoyman.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div><div></div><div class="h5">On Wed, Feb 2, 2011 at 2:50 PM, Aristid Breitkreuz<br>
<<a href="mailto:aristidb@googlemail.com">aristidb@googlemail.com</a>> wrote:<br>
> I agree with most things.<br>
><br>
> 2011/2/2 Michael Snoyman <<a href="mailto:michael@snoyman.com">michael@snoyman.com</a>><br>
>><br>
>> * Request and response datatypes themselves. I don't think this makes<br>
>> sense to put in http-types: just between WAI and http-enumerator I<br>
>> needed different versions of these.<br>
><br>
> I think this is where we could derive most value, and it would be good to<br>
> find a way to do it.<br>
> Request actually looks pretty similar in WAI as in http-enumerator, but<br>
> Response is different. Maybe distinguish between client and server versions<br>
> of Response?<br>
<br>
</div></div>I'd be very surprised if those two can be meaningfully unified. What<br>
do you do about remoteHost and errorHandler? Also, it's more useful to<br>
have the request body for http-enumerator be an Enumerator of<br>
Builders, as opposed to WAI where we want an Enumerator of<br>
ByteStrings.<br>
<br>
I have no opposition to *having* a Request type in http-types (or<br>
whatever we call it), but I doubt anyone will actually use it, and I<br>
wouldn't even want it to include Builder due to the extra dependency.<br>
<font color="#888888"><br>
Michael<br>
</font></blockquote></div><br></div></div>