This project has moved and is read-only. For the latest updates, please go here.

Using Nito TcpClient with shift-jis encoding

Mar 9, 2012 at 11:57 AM


I'm currently looking into using Nito.Async, so I'm really new to this.

I have had a look at the examples for communicating via sockets. It looks like it is using a base64 encoding.

My problem is that I need to communicate with a server that uses the japanese shift-jis encoding (In fact I have to support many encodings)
I cannot change this fact, so I have to make a client that sends and reads text in shift-jis encoding.

Does anybody have experience with that? Is it possible to use Nito.Async then?

Thanks in advance

Lars Iversen

Mar 18, 2012 at 10:17 PM

Nito.Async.Sockets have two levels of abstraction:

All of the types starting with "Simple" implement a simple, specific protocol. They can only be used with the other "Simple" types.

The other types (including ClientTcpSocket, ServerTcpSocket, and ServerChildTcpSocket) are general socket types. They operate on binary data, so you can use whatever encoding you want.