Design a wire protocol for non RESTFul transports

Registered by Flavio Percoco

We currently have a well defined protocol that works well for HTTP. As a project, we're looking forward to welcome more transports that will work for different use-cases but we don't have a way to support them. This blueprint aims to define such protocol and the work needed to make it happen.

https://github.com/openstack/zaqar-specs/blob/master/specs/kilo/approved/define-a-wire-protocol.rst

Blueprint information

Status:
Complete
Approver:
Flavio Percoco
Priority:
Medium
Drafter:
Victoria Martinez de la Cruz
Direction:
Approved
Assignee:
Victoria Martinez de la Cruz
Definition:
Approved
Series goal:
Accepted for kilo
Implementation:
Implemented
Milestone target:
milestone icon 2015.1.0
Started by
Victoria Martinez de la Cruz
Completed by
Flavio Percoco

Related branches

Sprints

Whiteboard

The definition for the wire transport protocol can be found in the following wiki page.

https://wiki.openstack.org/wiki/Zaqar/specs/Protocols/Wire_Transport

The message format has been designed to be as compatible as possible with the one used for the WSGI transport. This work has been addressed by flaper87 as part of the design of the ZMQ transport driver.

The connection and the security details for wire transports hasn't been defined in order to support multiple implementations.
-- vkmc

I've updated the example and spec in the wiki page
-- flaper87 2014-12-16

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.