You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
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
orcettia-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
The text was updated successfully, but these errors were encountered: