<p>Just make sure Cookie handling can be disabled completely.<br></p>
<p>Aristid </p>
<div class="gmail_quote">Am 23.01.2012 07:44 schrieb "Michael Snoyman" <<a href="mailto:michael@snoyman.com">michael@snoyman.com</a>>:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On Mon, Jan 23, 2012 at 8:31 AM, Myles C. Maxfield<br>
<<a href="mailto:myles.maxfield@gmail.com">myles.maxfield@gmail.com</a>> wrote:<br>
> 1. Oops - I overlooked the fact that the redirectCount attribute of a<br>
> Request is exported (it isn't listed on the documentation probably because<br>
> the constructor itself isn't exported. This seems like a flaw in<br>
> Haddock...). Silly me. No need to export httpRaw.<br>
><br>
> 2. I think that stuffing many arguments into the 'http' function is ugly.<br>
> However, I'm not sure that the number of arguments to 'http' could ever<br>
> reach an unreasonably large amount. Perhaps I have bad foresight, but I<br>
> personally feel that adding cookies to the http request will be the last<br>
> thing that we will need to add. Putting a bound on this growth of arguments<br>
<br>
I completely disagree here. If we'd followed this approach, rawBody,<br>
decompress, redirectCount, and checkStatus all would have been<br>
arguments. There's a reason we use a settings data type[1] here.<br>
<br>
[1] <a href="http://www.yesodweb.com/blog/2011/10/settings-types" target="_blank">http://www.yesodweb.com/blog/2011/10/settings-types</a><br>
<br>
> makes me more willing to think about this option. On the other hand, using a<br>
> BrowserAction to modify internal state is very elegant. Which approach do<br>
> you think is best? I think I'm leaning toward the upper-level Browser module<br>
> idea.<br>
><br>
> If there was to be a higher-level HTTP library, I would argue that the<br>
> redirection code should be moved into it, and the only high-level function<br>
> that the Network.HTTP.Conduit module would export is 'http' (or httpRaw).<br>
> What do you think about this?<br>
<br>
I actually don't want to move the redirection code out from where it<br>
is right now. I think that redirection *is* a basic part of HTTP. I'd<br>
be more in favor of just bundling cookies in with the current API,<br>
possibly with the IORef approach I'd mentioned (unless someone wants<br>
to give a different idea). Having a single API that provides both<br>
high-level and low-level approaches seems like a win to me.<br>
<br>
Michael<br>
<br>
_______________________________________________<br>
Haskell-Cafe mailing list<br>
<a href="mailto:Haskell-Cafe@haskell.org">Haskell-Cafe@haskell.org</a><br>
<a href="http://www.haskell.org/mailman/listinfo/haskell-cafe" target="_blank">http://www.haskell.org/mailman/listinfo/haskell-cafe</a><br>
</blockquote></div>