The new net/http-client library addresses the problems in this thread. Jay
On Sat, Jul 13, 2013 at 8:07 PM, Eli Barzilay <e...@barzilay.org> wrote: > Regardless of specs, it's useful to be able to talk to servers even > when they're misbehaving. A nice possible way to deal with this is to > expose some more primitive layer using raw strings. > > > > Two days ago, Jay McCarthy wrote: >> This debate is bigger than you and me, but I don't see a spec >> here. I see a weird pseudo-code parsing algorithm with no >> specification. In any case, the net/url module implements the >> RFCs. If those aren't what you want, then it needs to be changed or >> a new module needs to be implemented. Given the big different >> between the RFCs and this new "specification", I gather there won't >> be a lot of shared code. >> >> Jay >> >> On Thu, Jul 11, 2013 at 12:16 PM, Sam Tobin-Hochstadt <sa...@ccs.neu.edu> >> wrote: >> > I'm not sure which spec you're looking at from there, but the URL >> > spec that I linked to is the most current work on precisely >> > specifying URLs. > > -- > ((lambda (x) (x x)) (lambda (x) (x x))) Eli Barzilay: > http://barzilay.org/ Maze is Life! -- Jay McCarthy <j...@cs.byu.edu> Assistant Professor / Brigham Young University http://faculty.cs.byu.edu/~jay "The glory of God is Intelligence" - D&C 93 ____________________ Racket Users list: http://lists.racket-lang.org/users
