Difference between revisions of "Zaqar/specs/endpoint"
< Zaqar
| Line 4: | Line 4: | ||
Endpoints represent a communication layer between Marconi and external clients. They exist in order to support multiple transports like HTTP, ZMQ, etc; they are not exclusive and can be enabled directly from the config file. | Endpoints represent a communication layer between Marconi and external clients. They exist in order to support multiple transports like HTTP, ZMQ, etc; they are not exclusive and can be enabled directly from the config file. | ||
| − | Each endpoint defines its own API that is common in terms of methods but different in terms of implementation. | + | Each endpoint defines its own API that is common in terms of methods but different in terms of implementation and inherits from an abstract endpoint class that defines methods that should be call by endpoints after translating requests to something useful for Marconi. |
| + | |||
| + | For specific implementations read: [http://wiki.openstack.org/marconi/specs/api/v1 HTTP], [http://wiki.openstack.org/marconi/specs/zmq/api/v1 ZMQ] | ||
Revision as of 08:02, 20 February 2013
Marconi Endpoints
Endpoints represent a communication layer between Marconi and external clients. They exist in order to support multiple transports like HTTP, ZMQ, etc; they are not exclusive and can be enabled directly from the config file.
Each endpoint defines its own API that is common in terms of methods but different in terms of implementation and inherits from an abstract endpoint class that defines methods that should be call by endpoints after translating requests to something useful for Marconi.
