On Fri, Jan 16, 2009 at 8:11 PM, Sigbjorn Finne <sigbjorn.fi...@gmail.com> wrote: > I'm guessing that you are reading something different into that > than what's intended - it's "client-side" in the sense that it can > only issue web requests and handle their responses. i.e., it > doesn't handle incoming HTTP requests and issue suitable > responses. Web server implementation is an interesting problem > in its own right, and many packages/frameworks do an > admirable job of that already, so no plans (by me) to tackle > that via the HTTP package. > > But, utilizing the HTTP package as part of any web app you > expose on a web server is very much on and not out of bounds. > Go for it! :-) > > Does that answer your Q? (my apologies if I'm stating the > obvious above.)
Thanks for your reply Sigbjorn. Correct me if I am wrong, but it seems to me that by using sockets for incoming connections and receiveHTTP :: Stream s => s -> IO (Result Request_String) and respondHTTP :: Stream s => s -> Response_String -> IO () from Network.HTTP.Stream that I could easily handle incoming requests and send responses back. OK, I need to build up the response myself, but that would be no real limitation for me. Thanks again, Levi _______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe