Cookies improve the way our website works, by using this website you are agreeing to our use of cookies. For more information see our privacy policy. OK

CRecordTcpDeleteServer

A TCP server can be destroyed with a message.
This is a nano service in the SYSTEM namespace.

The TCP server can be identified by its ID or by port. 

{
  "id": "b5704abf-f279-4220-8a0d-3d937e7d341e",
  "name": "TCP_DELETE_SERVER",
  "isNanoService": "true",
  "type": "REQUEST",
  "hasOtherSlots": "false",
  "description": "Close and delete a TCP server.",
  "namespaces": "SYSTEM",
  "slots": [
    {
      "key": "1",
      "name": "ID",
      "direction": "REQUEST",
      "presenceConstraint": "CONDITIONAL_EXCLUSIVE",
      "type": "UUID",
      "description": "The server ID. If the server ID is not specified, the port is used for selection."
    },
    {
      "key": "2",
      "name": "PORT",
      "direction": "REQUEST",
      "presenceConstraint": "CONDITIONAL_EXCLUSIVE",
      "type": "INT",
      "description": "The server port. If the server port is not specified, the server ID is used for selection."
    }
  ]
}

Slot Description

Key Name Direction Presence Constraint Type Description
1 ID REQUEST CONDITIONAL_EXCLUSIVE UUID The server ID. If the server ID is not specified, the port is used for selection.
2 PORT REQUEST CONDITIONAL_EXCLUSIVE INT The server port. If the server port is not specified, the server ID is used for selection.

Record Usage

In nyssr.net, we typically don't exchange interfaces between projects. Instead, we use platform-independent Records to describe message formats.

One or more descriptions of these Records are stored in the JSON or XML format as record.json or record.xml within a directory. The Record Generator, an included Swing tool, generates helper classes from these files. These classes can then be used to type-safely write or read messages.

See also