Ability to set protocol ID? about netcode.io-browser

[gafferongames]

Yes. Apps definitely need to set their own protocol id!

[hach-que]

Isn't the protocol ID entirely set by the server and connection token generator?

None of the client functions the C implementation of netcode.io accept a protocol ID.

[hach-que]

(None of the browser code generates tokens or acts as a server, which is why the protocol ID doesn't appear in any of the APIs)

[gafferongames]

Good point. My idea of usage was that the client would pass up protocol ID to the rest call to the server (to enable multiple versions of the game being served in parallel from the same backend), and then this protocol ID would be incorporated into the token and passed down to the client.

[hach-que]

Yeah, how the client obtains the connect token is totally up to the application and not something the browser API covers.

[GlaireDaggers]

Ah, I get it now. Another pass over the C code reveals that, in fact, it does just retrieve protocol ID from the connect token (whereas in my .NET implementation it takes a protocol ID in the constructor and rejects connect tokens with mismatching protocol IDs in the Connect function). I might just go ahead and remove the protocol ID from my .NET version as well, and just grab it out of the connect token. Sorry to raise the apparent non-issue then - I suppose a bit more digging on my part should have shown me what I needed to know >.>

[hach-que]

No worries ^_^