CRecordTcpDeleteClient

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

The TCP client can be identified by its ID or by host/port.

{
  "id": "ac09c42f-91e8-474b-ab53-152f5924b076",
  "name": "TCP_DELETE_CLIENT",
  "isNanoService": "true",
  "type": "REQUEST",
  "hasOtherSlots": "false",
  "description": "Close and delete a TCP client.",
  "namespaces": "SYSTEM",
  "slots": [
    {
      "key": "1",
      "name": "ID",
      "direction": "REQUEST",
      "presenceConstraint": "CONDITIONAL_EXCLUSIVE",
      "type": "UUID",
      "description": "The client ID."
    },
    {
      "key": "2",
      "name": "HOST",
      "direction": "REQUEST",
      "presenceConstraint": "CONDITIONAL_EXCLUSIVE",
      "type": "STRING",
      "description": "The client remote host will be taken if the ID is missing."
    },
    {
      "key": "3",
      "name": "PORT",
      "direction": "REQUEST",
      "presenceConstraint": "CONDITIONAL_EXCLUSIVE",
      "type": "INT",
      "description": "The client remote port will be taken if the ID is missing."
    }
  ]
}

Slot Description

Key Name Direction Presence Constraint Type Description
1 ID REQUEST CONDITIONAL_EXCLUSIVE UUID The client ID.
2 HOST REQUEST CONDITIONAL_EXCLUSIVE STRING The client remote host will be taken if the ID is missing.
3 PORT REQUEST CONDITIONAL_EXCLUSIVE INT The client remote port will be taken if the ID is missing.

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