socket.txt - Pastebin for Sharing Code and Text

TEXT 12

Socket.txt Guest on 6th April 2021 09:32:19 AM

Sockets
=======
Data-stream interface
---------------------
A simple method to export data through the network. The MORSE sockets
middleware will create one socket for each component. The service
``simulation.list_streams`` returns the list of available data streams, and the
service ``simulation.get_stream_port(<stream name>)`` returns the port number
associated to this stream.
Data is shared as JSON object, encoded in utf-8 strings. As such, when
exchanging data with a particular component using this middleware, it is
necessary to create a similar data structure to the ``local_data`` dictionary
in the component.
For example, when using telnet to connect to a
:doc:`waypoint actuator <../actuators/waypoint>`, you need to send a message
like the following::
$ telnet localhost 60000
{"x":3.0, "y":5.0, "z":0.0, "tolerance":0.5, "speed":2.0}
The socket data-stream interface is implemented in :py:mod:`morse.middleware.socket_datastream`.
.. note:: The port numbers used for the socket datastream interface start at 60000.
.. _socket_ds_configuration:
Configuration specificities
---------------------------
There is no special configuration parameter for the socket middleware.
Service interface
-----------------
Requests to components or MORSE itself can be sent through the socket interface.
The (ASCII) protocol is simple. Either::
id component service [parameters]
or::
id special
- ``id`` is a freely chosen request id. It is mainly useful to identify answers
from asynchronous services.
- ``component`` is the name of the component you want to invoke the service on.
.. note::
Services that control the whole simulator belong to the special component ``simulation``.
- ``service``: the name of the request to invoke.
- ``parameters`` (can be omitted if the request takes no argument): request
arguments in JSON format. Arguments must be enclosed in a list (*i.e.*, inside
brackets).
- ``special``: a special command, used to manipulate already existing requests.
Currently, the only special command is ``cancel`` (to abort a running
service)
MORSE answer follows this model::
id status [result]
- ``id`` the same id the client used to send the request,
- ``status``: one of the :py:mod:`morse.core.status` constants
- ``result``: a JSON-serialized result, if any.
Example::
$ telnet localhost 4000
Connected to localhost.
> req1 Human move [1.0, 2.0]
req1 OK
.. note:: The socket service interface listen by default on port 4000. If this
port is busy, MORSE will try to connect to the next 10 ports {4001-4010}
before giving up.
.. note:: Why 4000?? That's a good question! A free beer for the first one who finds out.
The socket service interface is implemented in :py:mod:`morse.middleware.socket_request_manager`.
Files
-----
- Python (data-stream): ``$MORSE_ROOT/src/morse/middleware/socket_datastream.py``
- Python (services): ``$MORSE_ROOT/src/morse/middleware/socket_request_manager.py``
.. _json: http://docs.python.org/library/json.html

Recent Pastes

Raw Paste

Sockets
=======

Data-stream interface
---------------------

A simple method to export data through the network. The MORSE sockets
middleware will create one socket for each component. The service
``simulation.list_streams`` returns the list of available data streams, and the
service ``simulation.get_stream_port(<stream name>)`` returns the port number
associated to this stream.

Data is shared as JSON object, encoded in utf-8 strings. As such, when
exchanging data with a particular component using this middleware, it is
necessary to create a similar data structure to the ``local_data`` dictionary
in the component.
For example, when using telnet to connect to a
:doc:`waypoint actuator <../actuators/waypoint>`, you need to send a message
like the following::

$ telnet localhost 60000
  {"x":3.0, "y":5.0, "z":0.0, "tolerance":0.5, "speed":2.0}

The socket data-stream interface is implemented in :py:mod:`morse.middleware.socket_datastream`.

.. note:: The port numbers used for the socket datastream interface start at 60000.

.. _socket_ds_configuration:

Configuration specificities
---------------------------

There is no special configuration parameter for the socket middleware.

Service interface
-----------------

Requests to components or MORSE itself can be sent through the socket interface.

The (ASCII) protocol is simple. Either::

id component service [parameters]

or::

id special

- ``id`` is a freely chosen request id. It is mainly useful to identify answers
  from asynchronous services.  
- ``component`` is the name of the component you want to invoke the service on.

.. note::
  Services that control the whole simulator belong to the special component ``simulation``.

- ``service``: the name of the request to invoke.
- ``parameters`` (can be omitted if the request takes no argument): request
  arguments in JSON format. Arguments must be enclosed in a list (*i.e.*, inside
  brackets).
- ``special``: a special command, used to manipulate already existing requests.
  Currently, the only special command is ``cancel`` (to abort a running
  service)

MORSE answer follows this model::

id status [result]

- ``id`` the same id the client used to send the request,
- ``status``: one of the :py:mod:`morse.core.status` constants
- ``result``: a JSON-serialized result, if any.

Example::

$ telnet localhost 4000
  Connected to localhost.
  > req1 Human move [1.0, 2.0]
  req1 OK

.. note:: The socket service interface listen by default on port 4000. If this
	port is busy, MORSE will try to connect to the next 10 ports {4001-4010}
	before giving up.

.. note:: Why 4000?? That's a good question! A free beer for the first one who finds out.

The socket service interface is implemented in :py:mod:`morse.middleware.socket_request_manager`.

Files
-----

- Python (data-stream): ``$MORSE_ROOT/src/morse/middleware/socket_datastream.py``
- Python (services): ``$MORSE_ROOT/src/morse/middleware/socket_request_manager.py``

.. _json: http://docs.python.org/library/json.html