CRecordTcpCreateClientRetry

A TCP client can be created using a message. A flag can be specified that you want to receive a notification in case of a new attempt to establish the connection. This record is the desired notification.

{
  "id": "ef1cf2a3-b501-404a-8545-394ae5b7a514",
  "name": "TCP_CREATE_CLIENT_RETRY",
  "isNanoService": "false",
  "type": "NOTIFICATION",
  "hasOtherSlots": "false",
  "description": "Begin of a new retry period for client connection.",
  "slots": [
    {
      "key": "1",
      "name": "ID",
      "direction": "REQUEST",
      "presenceConstraint": "MANDATORY",
      "type": "UUID",
      "description": "The client ID."
    },
    {
      "key": "2",
      "name": "TIMEOUT",
      "direction": "REQUEST",
      "presenceConstraint": "MANDATORY",
      "type": "LONG",
      "description": "The retry period in milliseconds."
    },
    {
      "key": "3",
      "name": "RETRY_COUNT",
      "direction": "REQUEST",
      "presenceConstraint": "MANDATORY",
      "type": "INT",
      "description": "The retry count."
    }
  ]
}

Slot Description

Key Name Direction Presence Constraint Type Description
1 ID REQUEST MANDATORY UUID The client ID.
2 TIMEOUT REQUEST MANDATORY LONG The retry period in milliseconds.
3 RETRY_COUNT REQUEST MANDATORY INT The retry count.

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