The first thing that a HTTaP client does, upon first connection to a server, is to check its configuration and characteristics. They are provided by a JSON object with these properties:
- HTTaP_version : returns an integer that describes the date in YYYYMMDD format (when displayed in decimal). Reading this property indicates that the server is HTTaP-compatible so this property is required.
- Type : returns a string that describes the server.
- ID : return a string that descibes the name or serial number of the server.
- Services : lists the available features that the server implements. For now it's a string but will become an object for a better (and hierarchical) description. Available services : Loopback, Files, ...
- Signals : lists the available signals that can be queried. Each can be a complex object.
- SessionID : integer number, generated randomly at each new connection. Used as a token for the persistent connection. For example, helps the client detect that the connection was interrupted.
More will appear as the protocol grows...