IRPCVault.NotifyDataPushEvent
Vault API / core write session
Notify for server data push message change. In multi-server mode this is broadcast to all nodes and node that has client channel open can continue operation.
| Service | Vault information MFiles.IRPCVault |
|---|---|
| gRPC method | /MFiles.IRPCVault/NotifyDataPushEvent |
| HTTP (mf-http-grpc) | POST /grpc/v1/notify-data-push-event |
| Request | NotifyDataPushEventRequest |
| Response | NotifyDataPushEventResponse |
| Book and level | Vault API, core |
| Kind | write |
| Session | Required: the session ID from LogIn in the mfiles-session-id-bin metadata. |
| Idempotent | no |
| Returns metadata structure version | no |
| Streaming | none (unary) |
Remarks
Part of server data push, used by M-Files clients and servers in multi-server deployments to pass a push event to the server that holds the client's push channel. Applications rarely need it.
Request: NotifyDataPushEventRequest
A structure that specifies notify data push event request.
Nested message fields are expanded to depth 3; follow a type link for deeper levels and for the type's own page.
| Field | Type | Description |
|---|---|---|
request_id | int32 | The request id, should match with the request id that was received from of the RequestPushDataAsync call. |
notify_type | ServerDataPushNotifyType | The notify type. 0 = unknown, 1 = request, 2 = response, 3 = hearbeat.Values: SERVER_DATA_PUSH_NOTIFY_TYPE_UNKNOWN (0), SERVER_DATA_PUSH_NOTIFY_TYPE_REQUEST (1), SERVER_DATA_PUSH_NOTIFY_TYPE_RESPONSE (2), SERVER_DATA_PUSH_NOTIFY_TYPE_HEARTBEAT (3). |
Response: NotifyDataPushEventResponse
The response of NotifyDataPushEvent. Has no data.
No fields.