NIM services: Difference between revisions

Line 800:

| 0x5 || 0x1 || Padding

|-

| 0x6 || 0x2 || u16 ~~size0~~. Must be <=0x1000.

| 0x6 || 0x2 || u16 meta_size. Must be <=0x1000.

|-

| 0x8 || 0x8 || s64 ~~size1~~. Must not be negative. During message-specific handling with request/reply this must also match the expected value (except for ID 0x0 which is ignored in this case).

| 0x8 || 0x8 || s64 data_size. Must not be negative. During message-specific handling with request/reply this must also match the expected value (except for ID 0x0 which is ignored in this case).

|}

After the header is the associated data for ~~size0~~ and ~~size1~~. The functions which generate the header always leave ~~size0~~ at value 0, when receiving the data for ~~size0~~ the received data is unused.

After the header is the associated data for meta_size and data_size. The functions which generate the header always leave meta_size at value 0, when receiving the data for meta_size the received data is unused.

The first message used by the client with SystemUpdate is ID 0x1.

Line 815:

{| class="wikitable" border="1"

|-

! ID || Request ~~size1~~ / data || Reply ~~size1~~ / data || Description

! ID || Request data_size / data || Reply data_size / data || Description

|-

| 0x0 || 0x0 || 0x0 || Tells the server to exit. When handling this the handler func will immediately return 0, without sending a reply.

@@ Line 800: / Line 800: @@
 | 0x5 || 0x1 || Padding
 |-
-| 0x6 || 0x2 || u16 size0. Must be <=0x1000.
+| 0x6 || 0x2 || u16 meta_size. Must be <=0x1000.
 |-
-| 0x8 || 0x8 || s64 size1. Must not be negative. During message-specific handling with request/reply this must also match the expected value (except for ID 0x0 which is ignored in this case).
+| 0x8 || 0x8 || s64 data_size. Must not be negative. During message-specific handling with request/reply this must also match the expected value (except for ID 0x0 which is ignored in this case).
 |}
-After the header is the associated data for size0 and size1. The functions which generate the header always leave size0 at value 0, when receiving the data for size0 the received data is unused.
+After the header is the associated data for meta_size and data_size. The functions which generate the header always leave meta_size at value 0, when receiving the data for meta_size the received data is unused.
 The first message used by the client with SystemUpdate is ID 0x1.
@@ Line 815: / Line 815: @@
 {| class="wikitable" border="1"
 |-
-! ID || Request size1 / data || Reply size1 / data || Description
+! ID || Request data_size / data || Reply data_size / data || Description
 |-
 | 0x0 || 0x0 || 0x0 || Tells the server to exit. When handling this the handler func will immediately return 0, without sending a reply.