FTN11: FutoIn - Implementation Feature Requirements
Version: 0.1
Copyright: 2014 FutoIn Project (http://futoin.org)
Authors: Andrey Galkin

1. Intro

Invoker and Executor implementation may not implement all required interfaces, but they are required to provide dummy placeholder, which still allow to operate. Below is a summary of required features for Invoker and Executor to be implemented.

Note: version of this specification also serves as implementation feature list to be used in dependency management.

2. Executor requirements

2.1. Service-side Executor requirements

• futoin.ping
• futoin.master.provider
• Client for futoin.auth.backend
• futoin.auth.consumer
• Client for futoin.acl.provider
• futoin.acl.consumer
• Client for futoin.defense.provider
• Interface Executor Concept
• Client for futoin.log
• futoin.burst
• HTTP and WebSocket end-point FTN5 HTTP integration

2.2. Client-side Executor requirements

• In-Channel futoin.ping
• In-Channel futoin.master.consumer
• Optional: FTN6 Interface Executor Concept
  • If not implemented, In-Channel Executor interfaces must be handled internally by Client-side implementation

3. Invoker requirements

3.1. Invoker requirements - Simple CCM

• Client-side Executor requirements (#3)
• Credentials or HMAC-based message security
• If interactive, support for "Unauthorized" error:
  • Client for futoin.auth.consumer
• Simple part of FTN7 Interface Invoker Concept
• Dummy API for futoin.burst
• Client for HTTP end-point FTN5 HTTP integration

3.2. Invoker requirements - Advanced CCM

• Invoker requirements - Simple CCM (#4)
• Both Credentials AND HMAC-based message security
• Full support FTN7 Interface Invoker Concept
• Full API for futoin.burst
• Client for WebSocket end-point FTN5 HTTP integration

=END OF SPEC=