Closed cmdrk closed 1 year ago
This PR threads ENet-style channels and message types through Overworld, which I'm broadly calling quality of service (QOS).
You can now specify the qos and channels in your rpc_info/0 callback like so:
#{ opcode => ?KS_ZONE_JOIN, c2s_handler => {?MODULE, join, 2}, s2c_call => join, encoder => ks_pb, qos => reliable, channel => 0 },
The WebSocket integration should safely ignore this feature.
This PR threads ENet-style channels and message types through Overworld, which I'm broadly calling quality of service (QOS).
You can now specify the qos and channels in your rpc_info/0 callback like so:
The WebSocket integration should safely ignore this feature.