Okay, the server side of the async logging service is working great. It''s blazingly fast. The client side, though, isn''t quite so pretty. If I use EM for the client side, then I don''t see any way of letting the program that is using the logging service to do the following: 1) connect to the service 2) perform regular program tasks 3) send a message 4) go back to regular program tasks It seems that in order to get messages sent, I will have to create a new connection, send the message, then exit the EM event loop, yes? Am I overlooking something here? So in this case, where the server is _never_ going to send anything back to the client. The communications are essentially one way, with the client just dumping logging messages to the server and then continuing with its execution, I''m better off writting the client side using the basic Socket primitives instead of on top of EM, yes? Thanks, Kirk Haines