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

CRecordTcpNotifyServerDeleted

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

{
    "id": "530077d6-83f8-4aaa-9710-896f7a07bbcb",
    "name": "TCP_NOTIFY_SERVER_DELETED",
    "isNanoService": "true",
    "type": "NOTIFICATION",
    "hasOtherSlots": "false",
    "description": "Notification that a TCP server has been deleted.",
    "namespaces": "SYSTEM",
    "slots": [
        {
            "key": "1",
            "name": "ID",
            "direction": "REQUEST",
            "presenceConstraint": "MANDATORY",
            "type": "UUID",
            "description": "The ID of the server."
        },
        {
            "key": "2",
            "name": "PORT",
            "direction": "REQUEST",
            "presenceConstraint": "MANDATORY",
            "type": "INT",
            "description": "The server port."
        }
    ]
}

Slot Description

Key Name Direction Presence Constraint Type Description
1 ID REQUEST MANDATORY UUID The ID of the server.
2 PORT REQUEST MANDATORY INT The server 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