Confirmedusers, Bureaucrats, editor, Administrators
1,795
edits
Modding:Network API: Difference between revisions
From Vintage Story Wiki
→ProtoContracts
(Removed redundant Register code, replaced the ImplicitFields with explicit [ProtoMember(1)] - makes future extensions of network packets *a lot* easier.) |
|||
| Line 58: | Line 58: | ||
</syntaxhighlight> | </syntaxhighlight> | ||
The argument we pass to <code>ProtoMember</code> is a unique unsigned integer called a tag, and it's used to identify the fields flagged for serialization. When the client receives the packet containing the serialized <code>ProtoContract</code>, it won't know the type of its members, and will identify them by the tag number. | The argument we pass to <code>ProtoMember</code> is a unique unsigned integer called a tag, and it's used to identify the fields flagged for serialization. When the client receives the packet containing the serialized <code>ProtoContract</code>, it won't know the type of its members, and will identify them by the tag number. We could also use the class header <code>[ProtoContract(ImplicitFields = ImplicitFields.AllPublic)]</code> and skip all [ProtoMember] tags to flag all public fields for serialization, then tags are assigned in alphabetic order. ProtoBuf is beyond the scope of this tutorial, but you can read more about this powerful library [https://developers.google.com/protocol-buffers/docs/csharptutorial here]. | ||
The fields in these classes hold the data we wish to send through our channel. We'll use <code>NetworkApiTestMessage</code> to encase the initial message from the server, while <code>NetWorkApiTestResponse</code> will be used by the Client to send its response. | The fields in these classes hold the data we wish to send through our channel. We'll use <code>NetworkApiTestMessage</code> to encase the initial message from the server, while <code>NetWorkApiTestResponse</code> will be used by the Client to send its response. | ||
