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

CRecordTcpNotifyClientCreated

This is a nano service in the SYSTEM namespace. It is a notification about the creation of a TCP client. Interested targets can stick an observer on the nano service and receive this notification. 

{
    "id": "f492cef7-aafd-4c79-8ec9-5c469e507b9c",
    "name": "TCP_NOTIFY_CLIENT_CREATED",
    "isNanoService": "true",
    "type": "NOTIFICATION",
    "hasOtherSlots": "false",
    "description": "Notification that a TCP client has been created.",
    "namespaces": "SYSTEM",
    "slots": [
        {
            "key": "1",
            "name": "ID",
            "answer": "false",
            "mandatory": "true",
            "type": "UUID",
            "description": "The ID of the client."
        },
        {
            "key": "2",
            "name": "HOST",
            "answer": "false",
            "mandatory": "true",
            "type": "STRING",
            "description": "The client host."
        },
        {
            "key": "3",
            "name": "PORT",
            "answer": "false",
            "mandatory": "true",
            "type": "INT",
            "description": "The client port."
        }
    ]
}

Slot Description

Key Name Direction Presence Constraint Type Description
1 ID REQUEST true UUID The ID of the client.
2 HOST REQUEST true STRING The client host.
3 PORT REQUEST true INT The client port.

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