|
Server
|
Server commands received by DataPublisher and sent by DataSubscriber.
Namespace: GSF.TimeSeries.Transport
Assembly: GSF.TimeSeries (in GSF.TimeSeries.dll) Version: 2.4.218-beta
SyntaxMembers| Member name | Value | Description |
|---|---|---|
| Authenticate | 0 | Authenticate command. |
| MetaDataRefresh | 1 | Meta data refresh command. |
| Subscribe | 2 | Subscribe command. |
| Unsubscribe | 3 | Unsubscribe command. |
| RotateCipherKeys | 4 | Rotate cipher keys. |
| UpdateProcessingInterval | 5 | Update processing interval. |
| DefineOperationalModes | 6 | Define operational modes for subscriber connection. |
| ConfirmNotification | 7 | Confirm receipt of a notification. |
| ConfirmBufferBlock | 8 | Confirm receipt of a buffer block measurement. |
| PublishCommandMeasurements | 9 | Provides measurements to the publisher over the command channel. |
| UserCommand00 | 208 | Code for handling user-defined commands. |
| UserCommand01 | 209 | Code for handling user-defined commands. |
| UserCommand02 | 210 | Code for handling user-defined commands. |
| UserCommand03 | 211 | Code for handling user-defined commands. |
| UserCommand04 | 212 | Code for handling user-defined commands. |
| UserCommand05 | 213 | Code for handling user-defined commands. |
| UserCommand06 | 214 | Code for handling user-defined commands. |
| UserCommand07 | 215 | Code for handling user-defined commands. |
| UserCommand08 | 216 | Code for handling user-defined commands. |
| UserCommand09 | 217 | Code for handling user-defined commands. |
| UserCommand10 | 218 | Code for handling user-defined commands. |
| UserCommand11 | 219 | Code for handling user-defined commands. |
| UserCommand12 | 220 | Code for handling user-defined commands. |
| UserCommand13 | 221 | Code for handling user-defined commands. |
| UserCommand14 | 222 | Code for handling user-defined commands. |
| UserCommand15 | 223 | Code for handling user-defined commands. |
Remarks
Solicited server commands will receive a Succeeded or Failed
response code along with an associated success or failure message. Message type for successful responses will be based
on server command - for example, server response for a successful MetaDataRefresh command will return a serialized
DataSet of the available server metadata. Message type for failed responses will always be a string of
text representing the error message.
See Also