yrift / jwebsocket

Automatically exported from code.google.com/p/jwebsocket
0 stars 0 forks source link

custom protocol support on top of jWebSocket protocol #42

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
jWebSocket server system should allow users to implement custom protocol 
support on top of jWebSocket protocol. 

The header token with metadata information can be introduced as a part of token 
data so that custom user plugins can understand those metadata and use it.

Original issue reported on code.google.com by mailtopu...@gmail.com on 18 Aug 2010 at 7:21

GoogleCodeExporter commented 8 years ago

Original comment by mailtopu...@gmail.com on 18 Aug 2010 at 7:22

GoogleCodeExporter commented 8 years ago
The web browsers are supposed to support websocket's "sub-protocol" tag very 
soon. Until this is acheived we can pass the desired sub-protocol via the URL 
as we currently do already. We have packet processors and a Token interface 
with various possible implementations. Let's try to keep this infrastructure.

Original comment by fivefeetfurther@gmail.com on 9 Sep 2010 at 1:19

GoogleCodeExporter commented 8 years ago
In addition to my aforementioned comment we also support custom protocols as 
you can see in our infrastructure diagrams. I'm wondering what is supposed to 
be out "on top" of our protocol?

Original comment by fivefeetfurther@gmail.com on 9 Sep 2010 at 1:37

GoogleCodeExporter commented 8 years ago

Original comment by fivefeetfurther@gmail.com on 14 Oct 2010 at 2:38