MsgDeliverEvent() example in the doc

Hi,
RTP6.2NC
I tried to figure out how to use the MsgDeliverEvent() to notify a client
waiting for data.
In the doc example for MsgDeliverEvent() the client prepares an event and
send it to the
server using MsgSend().
The server never replies to this message and the client would be
REPLY_BLOCKED
never receiving the pulse right ?

cheers, Peter

Peter Weber <pw@dolphin.de> wrote:

Hi,
RTP6.2NC
I tried to figure out how to use the MsgDeliverEvent() to notify a client
waiting for data.
In the doc example for MsgDeliverEvent() the client prepares an event and
send it to the
server using MsgSend().
The server never replies to this message and the client would be
REPLY_BLOCKED
never receiving the pulse right ?

I don’t have the docs in front of me right now, but IIRC the client prepares
the event and sends it to the server and (you are correct here) blocks.
however, the expectation is that the server REPLIES to the client, effectively
saying “thanks for the event, when the time is right I’ll send it back to you”.
This unblocks the client. Some time later, the server does the MsgDeliverEvent
to the client, and everyone’s happy.

Cheers,
-RK


Robert Krten, PARSE Software Devices +1 613 599 8316.
Realtime Systems Architecture, Books, Video-based and Instructor-led
Training and Consulting at www.parse.com.
Email my initials at parse dot com.

Thanks Robert,
BTW: Is there a macro/function available to identify exactly an client if I
receive a _PULSE_CODE_DISCONNECT
in the server side?
What I’m talk about is: I have to split the scoid from the pulse back into
nd/pid/tid which is normaly a kind of rcvid but
if I receive the pulse, the rcvid is not available (==0). I know that the
scoid is a combination of nd/pid but where I can
get the tid of the disconnecting thread?
cheers, Peter

“Robert Krten” <nospam88@parse.com> schrieb im Newsbeitrag
news:ag2640$8o9$1@inn.qnx.com

Peter Weber <> pw@dolphin.de> > wrote:
Hi,
RTP6.2NC
I tried to figure out how to use the MsgDeliverEvent() to notify a
client
waiting for data.
In the doc example for MsgDeliverEvent() the client prepares an event
and
send it to the
server using MsgSend().
The server never replies to this message and the client would be
REPLY_BLOCKED
never receiving the pulse right ?

I don’t have the docs in front of me right now, but IIRC the client
prepares
the event and sends it to the server and (you are correct here) blocks.
however, the expectation is that the server REPLIES to the client,
effectively
saying “thanks for the event, when the time is right I’ll send it back to
you”.
This unblocks the client. Some time later, the server does the
MsgDeliverEvent
to the client, and everyone’s happy.

Cheers,
-RK


Robert Krten, PARSE Software Devices +1 613 599 8316.
Realtime Systems Architecture, Books, Video-based and Instructor-led
Training and Consulting at > www.parse.com> .
Email my initials at parse dot com.