03:24:28 <stepcut> shapr: ping!
04:34:16 <shapr> stepcut: pong
11:27:40 <h_buildbot> Build for ghc-6.8.3 failed. Check http://buildbot.happstack.com/ for details.
11:28:50 <h_buildbot> Build for ghc-6.10.2 failed. Check http://buildbot.happstack.com/ for details.
11:31:30 <h_buildbot> Build for ghc-6.12.1 OK. Test suite ran. 7/75 test cases failed. Check http://buildbot.happstack.com/ for details.
11:35:40 <h_buildbot> Build for ghc-6.8.3 failed. Check http://buildbot.happstack.com/ for details.
12:56:45 <HugoDaniel> hello there
14:23:41 <stepcut> HugoDaniel: hello..
14:45:00 <HugoDaniel> hi stepcut
14:45:16 <HugoDaniel> did you manage to find someone to work out the apache look-alike interface for dir browsing ?
14:53:02 <stepcut> HugoDaniel: not yet
14:54:55 <HugoDaniel> are there any benchmarks of happs vs other http servers ? like apache, lighty, cherokee, etc... ?
14:56:14 <stepcut> nope
14:56:35 <stepcut> well, maybe, but I do not know of any
14:57:48 <stepcut> though, for serving static files off the disk, it is hopefully pretty fast now that we got sendfile() :p
15:04:20 <HugoDaniel> :)
15:04:31 <HugoDaniel> cherokee has a nice feature along with sendfile
15:04:44 <HugoDaniel> where it limits the max size of a file to send
15:05:22 <HugoDaniel> anyway, i could try to give a hand on that apache lookalike page
15:32:29 <st3pcut> HugoDaniel: yay! go for it!
15:34:26 <st3pcut> I can answer any questions you have
15:44:00 <HugoDaniel> ok nice
15:44:35 <st3pcut> was it clear what I meant about trying to split it into two pieces? the core and the renderer?
16:04:22 <HugoDaniel> yes
16:04:41 <st3pcut> sweet
16:04:41 <HugoDaniel> im going to answer the e-mail you sent
16:48:35 <HugoDaniel> i get a lot of this with happs:
16:48:38 <HugoDaniel> tcp4       0      0         TIME_WAIT
16:49:10 <st3pcut> I have no idea what that means
17:01:52 <HugoDaniel> in netstat
17:03:21 <st3pcut> yes, I recognized netstat, but I don't know what TIME_WAIT means or if it should be concerning
17:03:51 <HugoDaniel> it means that the socket was closed but the protocol still requires it to be open because it was not closed properly
17:03:55 <HugoDaniel> the connection was just dropped
17:04:12 <HugoDaniel> so its just there waiting for a timeout to happen
17:04:42 <st3pcut> ah
17:05:07 <st3pcut> yeah, I see happstack sometimes spit out errors about that too.. something about 'resource vanished' or something
17:05:21 <st3pcut> would be nice to get to the bottom of that
17:05:29 <HugoDaniel> hmm yes
17:05:36 <HugoDaniel> its probably an OS thing
17:05:39 <HugoDaniel> im not sure
17:05:41 <st3pcut> maybe
17:05:55 <st3pcut> perhaps the remote side is closing the connection, but happstack is not?
17:06:56 <st3pcut> the web browser will typically close the connection once it has received all the bytes it was expecting (based on the HTTP headers). But perhaps happstack is not closing the connection after sending all the bytes for some reason?
17:07:22 <st3pcut> (there is also some keep-alive stuff that comes into play as well..)