Namespace NMF.Glsp.Protocol.BaseProtocol
Classes
- ActionMessage
A general message serves as an envelope carrying an action to be transmitted between the client and the server via a DiagramServer.
- BaseAction
An action is a declarative description of a behavior that shall be invoked by the receiver upon receipt of the action. It is a plain data structure, and as such transferable between server and client. Actions contained in action messages are identified by their kind attribute. This attribute is required for all actions. Certain actions are meant to be sent from the client to the server or vice versa, while other actions can be sent both ways, by the client or the server. All actions must extend the default action interface.
- CompoundOperation
An operation that executes a list of operations.
- CustomOperation
Denotes a class for custom operations
- ExecutableAction
Denotes an action that can be executed
- Operation
Marker interface for operations.
- RejectAction
A reject action is a response fired to indicate that a request must be rejected.
- RequestAction
A request action is tied to the expectation of receiving a corresponding response action. The requestId property is used to match the received response with the original request.
- ResponseAction
A response action is sent to respond to a request action. The responseId must match the requestId of the preceding request. In case the responseId is empty or undefined, the action is handled as standalone, i.e. it was fired without a preceding request.