Closed Injac closed 8 years ago
The only doc meaningful for socketio is its js implementation. +1
发自我的 iPhone
在 2015年11月27日,21:22,Ilija Injac notifications@github.com 写道:
I have difficulties in even understanding the notation of the protocol specification. Is that intended? If you want people to adapt the protocol to different platforms, a real specification would be very helpful. Even an RFC is easier to read than what you have here. I don't expect an answer at all, because I see that this issue is not a big concern for the socket.io implementers. If so, it would be reflected in a better documentation. I think reverse-engineering of the protocol will be less error-prone than the docs. Hope to see some changes soon.
— Reply to this email directly or view it on GitHub.
@shuoli84 +1
@lnjac @shuoli84 @mrniko we're working on a proper RFC. This was more of an informal / quick guide that we wrote while implementing the JS parsers. I appreciate the feedback.
Btw, if you have examples of what your ideal specifications would be, please post them here.
I'm closing this in favor of #14, let's continue the discussion there.
I have difficulties in even understanding the notation of the protocol specification. Is that intended? If you want people to adapt the protocol to different platforms, a real specification would be very helpful. Even an RFC is easier to read than what you have here. I don't expect an answer at all, because I see that this issue is not a big concern for the socket.io implementers. If so, it would be reflected in a better documentation. I think reverse-engineering of the protocol will be less error-prone than the docs. Hope to see some changes soon.