SVC: Difference between revisions
Misson20000 (talk | contribs) m →Result codes: formatting fail (I'm used to markdown), and that probably shouldn't have been monospace anyway |
Misson20000 (talk | contribs) →svcReplyAndReceive: Add note about specifying pointer buffer via C descriptor |
||
| Line 887: | Line 887: | ||
Then it will wait until either of the passed sessions has an incoming message, is closed, a passed port has an incoming connection, or the timeout expires. | Then it will wait until either of the passed sessions has an incoming message, is closed, a passed port has an incoming connection, or the timeout expires. | ||
If there is an incoming message, it is copied to the TLS. | If there is an incoming message, it is copied to the TLS. | ||
If ReplyTarget is zero, the TLS should contain a blank message. If this message has a C descriptor, the buffer it points to will be used as the pointer buffer. See [[IPC_Marshalling#IPC_buffers]]. Note that a pointer buffer cannot be specified if ReplyTarget is not zero. | |||
After being validated, passed handles will be enumerated in order; even if a session has been closed, if one that appears earlier in the list has an incoming message, it will take priority and a result code of 0x0 will be returned. | After being validated, passed handles will be enumerated in order; even if a session has been closed, if one that appears earlier in the list has an incoming message, it will take priority and a result code of 0x0 will be returned. | ||