🚀 go-pugleaf

I think I'm getting to grips with these components now.  I've focused on the 
non-blocking mode so far.  One thing I had not realised, or taken on board, 
was that the client will get an exception if it opens the socket and the 
server isn't running, so the app has to retry at regular intervals.  Also I 
found that you have to process the read event (Socket->ReceiveBuf) otherwise 
you don't get another event signaled.

There is one question though at this moment in time.  The OnWrite event, 
does that simply notify the application that it can start writing to the 
socket after connection?  I thought it would notify after every write had 
completed?  In my tests the test app trace only shows one OnWrite event (for 
both client and server).

Paul.

2005-08-27 12:17:08:0396 : Listening....
2005-08-27 12:17:27:0033 : Get Socket....
2005-08-27 12:17:27:0033 : Connected
2005-08-27 12:17:27:0033 : Accept
2005-08-27 12:17:27:0033 : Write Event - Write Ready
2005-08-27 12:17:28:0425 : Send Buffer (NOTE: server sends packet every 
10sec)
2005-08-27 12:17:38:0429 : Send Buffer
2005-08-27 12:17:48:0434 : Send Buffer
2005-08-27 12:17:58:0438 : Send Buffer
2005-08-27 12:18:08:0442 : Send Buffer
2005-08-27 12:18:18:0447 : Send Buffer
2005-08-27 12:18:28:0451 : Send Buffer
2005-08-27 12:18:38:0456 : Send Buffer
2005-08-27 12:18:48:0460 : Send Buffer
2005-08-27 12:18:58:0464 : Send Buffer
2005-08-27 12:19:01:0939 : Read Event - Data Ready (NOTE: client sending 64K 
byte array....)
2005-08-27 12:19:01:0939 : Read Event - Data Ready
2005-08-27 12:19:01:0939 : Read Event - Data Ready
2005-08-27 12:19:01:0939 : Read Event - Data Ready
2005-08-27 12:19:01:0949 : Read Event - Data Ready
2005-08-27 12:19:01:0949 : Read Event - Data Ready
2005-08-27 12:19:01:0949 : Read Event - Data Ready
2005-08-27 12:19:01:0949 : Read Event - Data Ready
2005-08-27 12:19:08:0469 : Send Buffer