shmdb

A PoC of a SHM-centric point cloud server

Protocol Elements

Basic Protocol Functions

• Each protocol operation is fully specified as a single JSON object. In this way, multiple transport protocols can be instantiated. For example, a synchronous socket connection as well as a RESTful service.

• Each protocol entity is identified by a generally unique ID (guid). This holds for the name of shared memory objects, sessions, processing tasks and futures.

• Each message sent to the server should contain a session unless it is transmitted in the context of a session.

• Each response from the server contains at least fields status_code following HTTP status codes and message giving a human-readable message.

Operation CREATE (>= v0.2)

A message to create a shared memory buffer. It contains fields such as

Aspect	Description
Request	Contains fields such as size in bytes, dtype string, nickname and any other user-defined field
Response	status message containing guid field

Operation RELEASE (>= v0.2)

Operation STORE (>= v0.3)

Aspect	Description
Request	Contains field guid. File name is derived from guid and time. Stored together with attribute object
Response	future for the operation

Operation LIST (>= v0.2)

Aspect	Description
Request	-
Response	JSON array list_response

Operation LOAD (>= v0.3)