The spec already supports this by explicitly allowing for custom transports. That being said, there's no standard for WebSocket right now.
I feel like the specific transports should be their own specs TBH. That would allow a lot a flex around this stuff and it would decouple transport changes from main protocol changes.
I feel like the specific transports should be their own specs TBH. That would allow a lot a flex around this stuff and it would decouple transport changes from main protocol changes.