Page History

Protocol Terms

  Any binary protocol will require following things:

1. Version: This indicates the API version.

2. Request Type: This indicates API needs to invoke.

3. Correlation Id: This helps to relate request-response.

4. Object Type: What is the type of serialized object.

5. Response Type: It indicates whether a response is partial or complete.

6. ErrorCodes: It indicates the problem with API invocation.

7. Streaming support: To support the large request, response or continuous response.

8. Request Format: Api request and response.

9. Byte Order(Big Endian)

10. Chunk Response: Send large response in multiple chunks.

11. Continuous Response: Client can register(Observer pattern) for events and then server notify the client if those events occurMessage: Bytes which contains defined format.

12. Request: It indicates client's message

13. Response: It indicates server's message.

14. Request Format: Format of request api and its parameters, which client wants to invoke.

15. Response Format: Format for api return value, which client invoked.

16. Message: Set of bytes which contain the Message Header and Request/Response.

17. Byte Order(Big Endian)