@cmuratori Yeah you're right, iocp is the best shit ever. I really like how it interfaces with the file functions. Much better than bsd.
-
-
Replying to @sssmcgrath
@sssmcgrath It's an almost perfect API. I'm still not sure it _isn't_ actually perfect, because I'm not sure I know all the parts.2 replies 0 retweets 1 like -
Replying to @cmuratori
@cmuratori@sssmcgrath Like for a long time I didn't know it worked with sockets, until I found out you could cast sockets to handles.3 replies 0 retweets 0 likes -
Replying to @cmuratori
@cmuratori it's underlying socket implementation is basically the same as bsd's kqueue, but it applies to files properly, kqueue doesn't =(2 replies 0 retweets 1 like -
Replying to @sssmcgrath
@sssmcgrath All of those systems _were based on IOCP_. Unix didn't have shit for this until after IOCP, and then sun cloned it, IIRC.2 replies 0 retweets 0 likes -
Replying to @cmuratori
@cmuratori@sssmcgrath Now all Unixes have it but they all fucked it up in one way or another so it's not as good as IOCP.2 replies 0 retweets 0 likes -
Replying to @cmuratori
@cmuratori I'm not sure about api-wise, but I'm pretty sure freebsd's kqueue is more efficient for sockets1 reply 0 retweets 0 likes
@sssmcgrath Yeah I can't speak for the implementation, I can only say as far as API design is concerned.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.