APIs, concepts, guides, and more

rapidserver is an application that provide access to the RMP via the RapidCodeRemote services via a Remote Procedure Call (RPC) using gRPC. Client applications can communicate with a rapidserver instance from any operating system.

To be used with the following RMP variations:
  • Windows (rapidserver.exe)
  • INtime (rapidserver.rta)
  • Linux (rapidserver)

🔹 Services

🔹 Usage

To interact with a rapidserver instance, users must have 3 things:

  1. The corresponding .proto files for the desired services (and access to the Protoc compiler).
  2. The server's IP address.
  3. The port number the server is bound to.

With the .proto files, users can compile them into usable client code in their desired programming language using the Protocol Buffer compiler (protoc). The client code will come with the ability to create a gRPC channel and a client for each service. Channels can be established using the server's IP address and port number. Clients can then use established channels to make RPCs.

🔹 Command Line Arguments

  • -help displays a message describing the basic usage of the rapidserver and the available command line arguments
  • -grpc_port specifies the port this server binds to and listens for RPC requests on. Users will communicate with the rapidserver via this port and the IP address of the host it is running on.
  • -discovery_port specifies the port the server will listen to broadcast requests on. Only users using the RapidSequencerAPI for starting and discovering servers will use this port.
  • -name specifies the "human-friendly" name of the server.
  • -echo specifies if the request messages of each RPC should be echoed back in the header of the response messages. By default, the rapidserver does not echo back the request messages.