How to represent protocol header depends on each transport but now all supported transports including even socket are using URI's query component. However because user may use query as well to attach some information according to the original purpose of query as a component of URI, it might conflict with ones used to represent protocol header.
To avoid confusion, every query parameter representing protocol header should be prefixed with their protocol name such as cettia or cettia-transport. For example, from the point of view of http server, a URI of one of requests belonging to http streaming transport
http://localhost:8080/cettia/?user-foo=bar&transport=stream&id=${transport.id}&sid=${socket.id}
should be rewritten to
http://localhost:8080/cettia/?foo=bar&cettia-transport-name=stream&cettia-transport-id=${transport.id}&cettia-id=${socket.id}
How to represent protocol header depends on each transport but now all supported transports including even socket are using URI's query component. However because user may use query as well to attach some information according to the original purpose of query as a component of URI, it might conflict with ones used to represent protocol header.
To avoid confusion, every query parameter representing protocol header should be prefixed with their protocol name such as
cettiaorcettia-transport. For example, from the point of view of http server, a URI of one of requests belonging to http streaming transportshould be rewritten to