SimTX API/Packets/CatalogDeleteResult: Difference between revisions
Protocol v25 reference: CatalogDeleteResult Tag: Removed redirect |
Remove development history and server internals |
||
| Line 19: | Line 19: | ||
message CatalogDeleteResult { | message CatalogDeleteResult { | ||
reserved 2, 3; | reserved 2, 3; | ||
int64 request_id = 1; | int64 request_id = 1; | ||
int32 entry_id = 4; | int32 entry_id = 4; | ||
| Line 34: | Line 33: | ||
|} | |} | ||
Field numbers 2 and 3 are reserved; do not use them. | |||
== See also == | == See also == | ||
Latest revision as of 17:16, 24 October 2026
| Frame | ServerFrame, field 39
|
|---|---|
| Member | catalog_delete_result
|
| Direction | Server → client |
| Session | Control (catalog) |
| Roles | ROLE_CONTROL.
|
| Permission | None |
| Answers | CatalogDelete |
| Defined in | control.proto
|
CatalogDeleteResult confirms that a CatalogDelete removed the entry. Refusals arrive as Error.
Definition[edit | edit source]
message CatalogDeleteResult {
reserved 2, 3;
int64 request_id = 1;
int32 entry_id = 4;
}
Fields[edit | edit source]
| # | Field | Type | Description |
|---|---|---|---|
| 1 | request_id |
int64 |
The request this answers. |
| 4 | entry_id |
int32 |
The removed entry. |
Field numbers 2 and 3 are reserved; do not use them.