On Fri, Nov 09, 2007 at 12:39:37AM +0100, Hannah Schroeter [EMAIL PROTECTED]
wrote:
I see less problems with the writing away of the data sucked from the
web servers, as most Unix like systems write stuff asynchronously, so
the open(..., O_CREAT...), write() and close() calls won't be too
On Mon, Nov 12, 2007 at 06:38:33AM +0100, Marc Lehmann wrote:
On Fri, Nov 09, 2007 at 12:39:37AM +0100, Hannah Schroeter [EMAIL
PROTECTED] wrote:
I see less problems with the writing away of the data sucked from the
web servers, as most Unix like systems write stuff asynchronously, so
the
On Sun, Nov 11, 2007 at 09:46:43PM -0800, Christopher Layne [EMAIL PROTECTED]
wrote:
Most unix systems cache data for quite long, butwhen they write, usually
user mode apps also halt. For throughput this is of little concern, but
in a game server I wrote, even an fsync could freeze the
http://sfbay.craigslist.org/pen/cpg/472325599.html
libevent programmer wanted (san mateo)
Reply to: [EMAIL PROTECTED]
Date: 2007-11-07, 8:33PM PST
I'm guessing if you clicked on this link, you probably know what
libevent is, and you're probably more than proficient in C. I have a
small project
Hi!
On Thu, Nov 08, 2007 at 02:19:25PM -0800, Christopher Layne wrote:
On Thu, Nov 08, 2007 at 08:11:55AM -0800, Garth Patil wrote:
http://sfbay.craigslist.org/pen/cpg/472325599.html
libevent programmer wanted (san mateo)
- NOT BLOCK ON ANY STEP
close() can block. *boom tsst*.
On sockets,
