0.5 Roadmap

[xaviervia]

Moved from jstp/jstp-rfc#17

3. Engine

3.1 Answer

Instructions to Engines to:

• Identify the Emitters willingness to receive an Answer (by storing a provided Answer Callback, IF there is an Answer Callback).
• Generate the Transaction ID.
• Bind the correct Endpoints for the Answer to be received.
• Upon processing of the Answer, Release the Endpoints. (the releasing of endpoints implies the maintainance of a table of Subscriptions triggered by the Source Dispatch, so that Answers from those Subscriptions can be received and subsequently the general Subscription to the Answer Endpoint can be released. Also, the Engine must timeout the answers if none is issued and respond with a Protocol Level 504 Timeout Status Code)

3.2 Robustness

Instructions to Engines to:

• Always attempt to reconnect lost outgoing connections to remote engines. Should the Answer be a special class in the specification? #6
• Once reconnected, always forward the Endpoints which are currently bound locally but are aimed at the remote engine. Should the Answer be a special class in the specification? #6

Introduction of the Engine programming API descriptions:

• The #dispatch method

3.3 Security & Usability

Intruction to Engines to provide a configuration tool for the developer to configure the default behaviours, specifically:

• Automatic gateway functionality
• Implementation Disclosure (for the 5xx Status Codes in the Answer Dispatches).
• Automatic reconnection attempt
• Reconnection attempt timespan