S-MethodInvoke

S-MethodInvoke

This primitive is used to request an operation to be executed by the server. It can only be used
together with another primitive, namely S-MethodResult. The S-MethodInvoke consists of, among
other things, identification numbers for the client and server to distinguish between pending
transactions. Another information the primitive contains is what kind of method the client wants to
invoke on the server: either an HTTP method or one of the extension methods established during
capability negotiation.
The S-MethodInvoke request is sent and when a confirmation is received from the server the client
waits for the requested data. The data is received in a primitive called S-MethodResult.

S-MethodResult

This primitive is used to return a response to an operation request made by a preceding SMethodInvoke
request. The S-MethodResult primitive consists of identification numbers that must
match the corresponding S-MethodInvoke primitive. This can be and is used to distinguish between
pending transactions.If one or other reason aborts a transaction, an S-MethodAbort.indication will be delivered to the service user. If this happens no further primitives related to the transaction can occur.

S-Suspend and S-Resume

These primitives work together but only in the obvious order: S-Suspend before s-Resume. A
suspension typically would be requested when the client know it will not be able to respond to data
pushes. The suspension can be broken either by a S-Resume or a S-Disconnect.

 Push facility

There is several primitives that handle the server push function, used for pushing unrequested data
from the server to the client, but no further discussion about them is taken here.