- File based NIO - Give the option of connect and read timeouts so that - unresponsive/hung/loaded servers performance can be logged. Perhaps NioSocket shd be simplified. I shd extend NioSocket and add read_complete, write_complete and handle_terminate there. If a user wants to process handle_read as data comes, this would confuse and make it difficult for him. Also, in Nio we forgot to buffer the output, assuming it would be small (4096). Allow for size to be set. Add output buffering also. WHY ARENT METHODS IN Server.java OVERRIDING THOSE IN NIOS ??? check return value: 200 is okay. we need to log errors so that users knows (particularly in SocketBlaster) that the server couldnt handle. 1. -1 with 0 bytes 2. Errors like 500,5* etc. create a handler and pass that Put option handling into a class so we can adde to that optimize SB, so that all repetitive tasks are done once only. Then add options to it for repeated bursts and incremental bursts. logging how many could not make it (refused) etc users may want to go through proxy for some urls and bypass for some. we cd take care of that. (PROXY HANDLING IS NOT OUR PRIORITY HERE!!!)