Ray Racine wrote:
My test case is pretty easy on my side, but I'm struggling for a simple
test case for the Larceny developers to test cross O/S.
I think we can proceed on the basis of what you've
already given us. OTOH, we may have a SIGPIPE put
Larceny in the debugger by default, just as a
On Sun, 2008-05-18 at 23:18 -0500, Chris Brannon wrote:
Are you checking the return value of write(2), to make sure that you don't
do a partially successful write? Most people only check for a negative
return value, assuming that they check at all. If your write(2) call
doesn't write all
I have been doing some load testing, lots of threads/tasks with lots of
socket io on my Larceny WebServer.
Current test goes like this:
1. Client (browser, curl hammer scripts) makes an HTTP request to my
Larceny WebServer.
2. The Larceny server in handling the request opens additional out
