Network application protocol based on event and semantic message streams
One user said, "Socket.D is to Socket what Vue is to Js and Mvc is to Http."
comparison | socket.d | http | websocket | rsocket | socket.io |
---|---|---|---|---|---|
Send (Qos0) | Yes | No | Yes | Yes | Yes |
SendAndRequest (Qos1) | Yes | Yes | No | Yes | No |
SendAndSubscribe (stream) | Yes | No | No | Yes | No |
Reply or respond | Yes | Yes | No | Yes | No |
Single connection two-way communication | Yes | No | Yes(trouble) | Yes | Yes(trouble) |
Data sharding | Yes | / | No | Yes | Yes |
Disconnection automatically reconnect | Yes | / | No | Yes | Yes |
Meta information | Yes | Yes | No | Yes | No |
Event(or path) | Yes | Yes | No | No | Yes |
StreamId (or message correlation) | Yes | No | No | Yes | No |
Broker pattern cluster | Yes | No | No | Yes | No |
Asynchronous | Async | Sync | Async | Async | Async |
Interface experience | Classic | Classic | Classic | Reactive(trouble) | Classic |
Basic transport protocol | tcp, udp, ws | tcp | http | tcp, udp, ws | ws |
It can be used for MSG, RPC, IM, MQ and other scenarios, and can replace Http, Websocket, gRpc and other protocols. Such as the connection between the mobile device and the server, such as some microservice scenarios, etc.
sd:tcp://19.10.2.3:9812/path?u=noear&t=1234
sd:udp://19.10.2.3:9812/path?u=noear&t=1234
sd:ws://19.10.2.3:1023/path?u=noear&t=1234
//udp only <2k
[len:int][flag:int][sid:str(<64)][\n][event:str(<512)][\n][metaString:str(<4k)][\n][data:byte(<16m)]
QQ communication group:870505482 | Wechat Communication group (input: SocketD when applying) |
---|---|
In the communication group, "nanny level" support and help are provided. Technical training and consultancy services are also available if required
此处可能存在不合适展示的内容,页面不予展示。您可通过相关编辑功能自查并修改。
如您确认内容无涉及 不当用语 / 纯广告导流 / 暴力 / 低俗色情 / 侵权 / 盗版 / 虚假 / 无价值内容或违法国家有关法律法规的内容,可点击提交进行申诉,我们将尽快为您处理。