eeoam: > Bryan O'Sullivan wrote: > >Eric wrote: > > > >>I'm writing a simple HTTP server and am trying to implement the POST > >>method. > > > >That's a rather general problem statement, indeed :-) For an > >application like this, I'd suggest that explicit resource management > >is the way to go, and that you should not be using hGetContents at > >all, under any guise. For example, any scheme involving reading an > >entire stream is going to do completely the wrong thing in the face of > >HTTP keepalive. Also, code that leaves open sockets piling up in > >drifts, to eventually be shoveled up by the RTS, is going to be > >trivially easy to DoS. > Are there any good resources/tutorials on Haskell network programming? > > E.
Some articles have been written here, http://haskell.org/haskellwiki/Blog_articles#Network Intro stuff mostly. See also HAppS, and Simon Marlow's concurrent webserver paper. -- Don _______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe