SmartSockets .NET Class Library

TipcSrv Events

The events of the TipcSrv class are listed below. For a complete list of TipcSrv class members, see the TipcSrv Members topic.

Public Instance Events

TipcErrorEvent (inherited from TipcConnClient) Occurs when an error occurs on a connection. Connection Error events are raised when an unrecoverable error occurs. These errors include socket problems and network failures such as:
  • A read timeout has occured and the keep-alive then failed.
  • A write timeout has occured.
  • A read operation on the connection's socket failed. The most common cause of this error is that the process at the other end of the connection has destroyed its connection, which closed the socket.
  • A write operation on the connection's socket failed. The most common cause of this error is that the process at the other end of the connection has destroyed its connection, which closed the socket.
TipcMsgEvent (inherited from TipcConnClient) Occurs when a message is processed. Connection process events are raised while processing a message. This callback type is the most frequently used. A process delegate method is called for every of message received. When any message of any type is processed by calling process or mainLoop, the process callback is called.
TipcQueueEvent (inherited from TipcConnClient) Occurs with message queue events. Connection queue events are raised when a message is inserted into or deleted from a connection's message queue. Queue events are useful for watching the messages that have been read in from a connection's socket and inserted into the message queue, but not yet processed.
TipcReadEvent (inherited from TipcConnClient) Occurs when a message is read from a connection. Connection read events are raised when an incoming message is read from a connection's socket into the read buffer and first unpacked into a message. Read events are most commonly used for writing incoming messages to message files.
TipcSrvCreateEvent Occurs when a connection to RTserver is created. Server create callbacks are called when an RTclient creates either a full or warm connection to the RTserver. If an RTclient creates and destoys its connection to the RTserver many times, it should use server create handlers to create the other handlers needed in the connection to RTserver.
TipcSrvDestroyEvent Occurs when a connection to RTserver is destroyed. Server destroy callbacks are called when an RTclient destroys its connection to the RTserver, leaving either a warm connection or no connection. Server destroy callbacks are the opposite of server create callbacks. Server destroy handlers are useful for RTclients that need to know when the connection to the RTserver no longer has a valid socket, such as RTclients that are also GUI programs.
TipcWriteBufferChangeEvent (inherited from TipcConnClient) Occurs when the write buffer is accessed. Write buffer change events are raised when data is either flushed from the write buffer or written into write buffer THROUGH the message interface (i.e. with send(msg)) ONLY.
TipcWriteEvent (inherited from TipcConnClient) Occurs when a message is written to a connection. Connection write events are raised when an outgoing message is sent to a connection (that is, copied to a connection's write buffer). Write events are most commonly used for writing outgoing messages to message files.

See Also

TipcSrv Class | TIBCO.SMARTSOCKETS Namespace

Copyright © TIBCO Software Inc. All rights reserved