Because the KBEngine network protocolID are automatically generated by the system, if no matching SDK will be very difficult to access server.
So, KBE provides a mechanism to allow the user to customize the network protocolID.
(for example: the traditional protocol docking will have a table, describe all protocol, client matching protocol-table in the protocol and analysis)
<Client::onRemoteMethodCall> <!-- Scope of protocol, "Client::" It is the client's agreement，"onRemoteMethodCall" As the name protocol interface -->
<id> 506 </id> <!-- ProtocolID -->
<descr> 调用一个远程方法。 </descr> <!-- Protocol description -->
<!-- args types -->
<arg> INT32 </arg> <!-- xxx -->
...
</Client::onRemoteMethodCall>