Fastsocket Study Notes ~rpc ideas, object-oriented flexibility

First of all, thank the man from Sina, it developed this fastsocket is very good, not to mention the performance, say its use and philosophy is very let people praise, from the macroscopic view, it is more like a remote process called RPC, the server exposes some commands for the client to call, very flexible, and its concept, it will be the socket programming abstraction, so that developers do not care about the underlying communication mechanism, but only concerned about the application layer of development, such as the development of a user module, you do not care about how the socket link declaration, do not care about performance, you just develop and user-related content.

Take a look, I drew it myself, hehe

Take a look at Fastsocket's own example.

Server-side configuration is very flexible, no hard-coded way, direct configuration file to take care of

<configSections> <section name="Socketserver"type="Sodao.FastSocket.Server.Config.SocketServerConfig, Fastsocket.server"/> </configSections> <socketServer> <servers> <server name="binary"Port="8401"socketbuffersize="8192"messagebuffersize="8192"maxmessagesize="102400"MaxConnections="20000"servicetype="Server.myservice, Server"Protocol="asyncbinary"/> </servers> </socketServer>

Supports a variety of delivery standards, or protocols called

Asyncbinaryprotocol: Asynchronous Binary mode

Commandlineprotocol: command-line mode

Thriftprotocol:thrift mode

Well, this section is mainly about the concept of knowledge, including fastsocket design ideas, thank you for reading!

Fastsocket Study Notes ~rpc ideas, object-oriented flexibility