NY_RecordDatabase on sillysky.net

EPresenceConstraint

Mon, 01 Dec 2025 00:00:00 +0000

This enum contains values that indicate whether arguments are optional or mandatory.

public enum EPresenceConstraint
{
    /**
    * The slot must always be present and filled with a valid value.
    */
    MANDATORY,
    
    /**
    * The slot may be present or absent. Its presence is not required.
    */
    OPTIONAL,
    
    /**
    * The slot must be present only if a specific condition (e.g., another field's value) is met.
    */
    CONDITIONAL_REQUIRED,
    
    /**
    * The slot is part of an exclusive group: either this slot OR one of the related slots must be present.
    */
    CONDITIONAL_EXCLUSIVE
}

ERecordType

Mon, 01 Dec 2025 00:00:00 +0000

This enumeration describes the type of record and thus the message.

public enum ERecordType
{
    REQUEST,
    NOTIFICATION,
    DATA_CONTAINER
}

Description

Request

A Request, in information technology, refers to a message sent from a client to a server to initiate a specific action, request a resource, or transmit data. A response from the receiver is usually expected, containing either the requested data, a confirmation of the action performed, or status information.

Notification

A Notification serves as an essential means of communication in software development, particularly in the context of distributed systems and reactive architectures. It informs observers about an event or a state change in a subject that they have previously subscribed to. This pattern, known as the Observer Pattern, enables loose coupling between components, as the subject (the sender) does not need to know which specific observers (the receivers) exist. It is only responsible for dispatching the notification as soon as a relevant event occurs—for example, the update of a data set, the completion of a process, or a critical system alert. By using notifications, multiple interested components can react synchronously to a single change without the original subject having to explicitly call each individual component. This significantly increases the flexibility, maintainability, and scalability of the application.

ETransportDirection

Mon, 01 Dec 2025 00:00:00 +0000

The ETransportDirection enumeration describes the transport direction of messages. The enum distinguishes between Request, Response, and Both, i.e., for the outward and return journeys.

public enum ETransportDirection
{
    /**
    * Direction: From sender to receiver.
    */
    REQUEST,
    
    /**
    * Direction: From receiver to sender.
    */
    RESPONSE,
    
    /**
    * Direction: BOTH directions.
    */
    BOTH
}

NY_RecordDatabase on sillysky.net

EPresenceConstraint

ERecordType

Description

Request

Notification

ETransportDirection

See also