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
Add a way for extensions to specify the packets it is interested in. That way the extension server doesn't have to forward every single packet, but only those the extension actually is interested in.
I would like to work on this once my PR for rewriting the network extensions code (#137) is merged.
The text was updated successfully, but these errors were encountered:
since this would probably break backward compatibility with older extensions, we need to make sure this has practical benefit, perhaps with some small benchmarking
I was thinking we we could add an optional NetworkMessage with a list of all the packet identifiers the extensions needs.
Then the network server only forwards those, in case it receives no such message from the client, it just operates as it did before. So backward compatibility should remain intact. I think
Add a way for extensions to specify the packets it is interested in. That way the extension server doesn't have to forward every single packet, but only those the extension actually is interested in.
I would like to work on this once my PR for rewriting the network extensions code (#137) is merged.
The text was updated successfully, but these errors were encountered: