Version 1.1 now posted supports .NET Encodings for strings so you can now transfer Unicode, or other code page, strings from the client to a server that can accept them. This may be partcularly useful for commands that can only be tranferred as strings and with the default settings are restricted to 128 character ASCII coding. I thought that there might be encodings settings for both client and server and after poking around I found them!
The server Processed property is now documented and a minor bug associated with it's use fixed.