The following functions require a send tokens:
gm_datagram_send()
gm_directed_send()
gm_directed_send_with_callback()
gm_drop_sends()
gm_resume_sending()
gm_send()
gm_send_to_peer()
gm_send_to_peer_with_callback()
gm_send_with_callback()
The send token is implicitly returned to the client when the function's
callback is called or, for the GM-1.0 functions gm_send() and
gm_send_to_peer(), a send token is implicitly passed to the
client with each pointer returned in a GM_SENT_EVENT.
(The legacy GM_SENT_EVENTs are generated if and only if the legacy
gm_send() and gm_send_to_peer() functions are called.)
The following functions require a receive token:
gm_provide_receive_buffer()
gm_provide_receive_buffer_with_tag()
A single receive token is passed to the client with each of the following events:
GM_RAW_RECV_EVENT
GM_RECV_EVENT
GM_HIGH_RECV_EVENT
GM_HIGH_PEER_RECV_EVENT
GM_FAST_HIGH_RECV_EVENT
GM_FAST_HIGH_PEER_RECV_EVENT
(However, if the client passes these event to gm_unknown(), then the
token is implicitly returned to GM.) Any of the GM receive functions
can generate these types of events. These functions are:
gm_receive()
gm_blocking_receive()
gm_blocking_receive_no_spin()
Go to the first, previous, next, last section, table of contents.