rpcmessage: Part attribute value fixed

silicon-heaven · Feb 11, 2024 · eb45d48 · eb45d48
1 parent 02a04af
commit eb45d48
Showing 1 changed file with 11 additions and 11 deletions.
diff --git a/src/rpcmessage.md b/src/rpcmessage.md
@@ -11,17 +11,17 @@ RPC message can have meta-data attribute defined.
 
 Attribute number | Attribute name      | Description
 ----------------:|---------------------|------------
-1                | metaTypeId          | Always equal to `1` in case of RPC message 
-2                | metaTypeNameSpaceId | Always equal to `0` in case of RPC message, may be omitted.
-8                | requestId           | Every RPC request must have unique number per client. Matching RPC response will have the same number. 
-9                | shvPath             | Path on which method will be called. 
-10               | method              | Name of called RPC method 
-11               | callerIds           | Internal attribute filled by broker in request message to distinguish requests with the same request ID, but issued by different clients.  
-13               | respCallerIds       | Internal attribute filled by broker in response message to enable support for multi-part messages and tunneling. https://github.com/silicon-heaven/libshv/wiki/multipart-messages
-14               | access              | Access granted by broker to called `shvPath` and `method` to current user. 
-16               | userId              | ID of user calling RPC method filled in by broker.
-17               | accessLevel         | Reserved, integer value, it will be used in next API version for chained brokers access capping  
-19               | part                | Reserved, it will be used in next API version for multi-part messages   https://github.com/silicon-heaven/libshv/wiki/multipart-messages
+1                | MetaTypeId          | Always equal to `1` in case of RPC message 
+2                | MetaTypeNameSpaceId | Always equal to `0` in case of RPC message, may be omitted.
+8                | RequestId           | Every RPC request must have unique number per client. Matching RPC response will have the same number. 
+9                | ShvPath             | Path on which method will be called. 
+10               | Method              | Name of called RPC method 
+11               | CallerIds           | Internal attribute filled by broker in request message to distinguish requests with the same request ID, but issued by different clients.  
+13               | RespCallerIds       | Internal attribute filled by broker in response message to enable support for multi-part messages and tunneling. https://github.com/silicon-heaven/libshv/wiki/multipart-messages
+14               | Access              | Access granted by broker to called `shvPath` and `method` to current user. 
+16               | UserId              | ID of user calling RPC method filled in by broker.
+17               | AccessLevel         | Reserved, integer value, it will be used in next API version for chained brokers access capping  
+18               | Part                | Reserved, it will be used in next API version for multi-part messages   https://github.com/silicon-heaven/libshv/wiki/multipart-messages
 
 Second part of RPC message is `IMap` with following possible keys.