Project Home
Project Home
Trackers
Trackers
Documents
Documents
Wiki
Wiki
Discussion Forums
Discussions
Project Information
Project Info
BroadcastCommunity.qnx.com will be offline from May 31 6:00pm until June 2 12:00AM for upcoming system upgrades. For more information please go to https://community.qnx.com/sf/discussion/do/listPosts/projects.bazaar/discussion.bazaar.topc28418
Forum Topic - Queston about "MsgDeliverEvent": Page 1 of 2 (2 Items)
   
Queston about "MsgDeliverEvent"  
Dear Experts.

I have a few questions. 

1. 
The sample code in QNX manual about MsgDeliverEvent() shows that "MsgReceivePulse" is used in client side to get event 
from server.  please refer to the sample code below:
http://www.qnx.com/developers/docs/6.3.2/neutrino/lib_ref/m/msgdeliverevent.html

Isn't it much easier to use "SignalWaitinfo" insteand of "MsgReceivePulse"?
What is difference between "SignalWaitinfo" and "MsgReceivePulse"
and what is the relation between "signal" and "pulse" in QNX neutrino? Does pulse is implemented by using "signal" or 
vice vesa  in QNX neutrino?

2. 
Once server get "rcvid" for a client, could this "rcvid" be used to call "MsgDeliverEvent" multi-times ? Or does it 
become invalid once "MsgDeliverEvent" is called?   I means, could Server keep use this "rcvid" to trigger MsgSend from 
client?  Does  "rcvid" value of client A is fixed as long as client A alive? or Is it changed whenever client A send a 
message ?

3. Is thereany issue if  I use MsgSendPulse/MsgSendReceive instead of  MsgDeliverEvent/SignalWaitinfo to trigger MsgSend
 from client ?

Thanks,
Dooeui