Simple message queue for Windows C application

Hello,

I'm hoping someone can provide a reference or example.

I have a multi-threaded application in C.  I'd like to use message queues to communicate between two of the threads and be able to pass messages of ~16 bytes.  I'm developing this under Windows right now but will port this to a different embedded operating system in the future.  I realize the thread and message queue functions will be different under a different operating system.

What I'm looking for is the simple way to do a message queue under Windows.  The MSDN literature immediately starts talking about GUI windows and system messages.  I'm not interested in either.

All I want to do is create the queue, pend a thread listening on the queue, and be able to write to it.

Any pointers or examples would be appreciated.

Thanks.
JohnSantaFeAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

jhp333Commented:
I think you're talking about message queues for IPC (Inter-Process Communication).
According to this page, http://msdn.microsoft.com/en-us/library/aa365574%28VS.85%29.aspx
Windows does not provide messages queues as a way of IPC.

You can try with user defined Windows messages, which are mainly for GUI by the way, but it's quite different from IPC message queue.
0
pgnatyukCommented:
>> I'm developing this under Windows right now but will port this to a different embedded operating system in the future

In case you want to send a message to the thread, you can do it with PostThreadMessage:
http://msdn.microsoft.com/en-us/library/ms644946(VS.85).aspx

For example :
PostThreadMessage(nThreadId, WM_MY_MESSAGE, wData, lData);

I'm sure, you can simply put these 16 bytes somewhere in a global variable protected with the critical section and call SetEvent in order to notify the thread about the new data coming.

About thread synchronization:
CodeProject. Thread Synchronization for Beginners
http://www.codeproject.com/KB/threads/Synchronization.aspx

0
cupCommented:
You could just use an STL queue if it is between threads.  Just do a mutex lock when performing the push and pop.

Since it is threads, they share the same address space so anything global will work.
0
Cloud Class® Course: MCSA MCSE Windows Server 2012

This course teaches how to install and configure Windows Server 2012 R2.  It is the first step on your path to becoming a Microsoft Certified Solutions Expert (MCSE).

xdomainsCommented:
If you are looking for a platform independent messaging library in C++, here is it -
http://www.sixtyfourbit.org/mq4cpp.htm

There are others as well, so depending on your requirement, need to select the right one.
0
JohnSantaFeAuthor Commented:
Hmmm.  I've used four other operating system that all had an inter-thread message queue as a fundamental component which other threads pend and wait on.  I'm surprised how difficult this seems under windows.

PostThreadMessage is close to what I'm use to, however, my receiving thread can't pend and wait for the message.

Maybe I'm not thinking of this in Windows terms.  My design problem is I have one thread listening to an ethernet port.  I have a second thread responding to commands that came in on the ethernet port and sending data out a slow serial link.  Because the serial link is slow, I don't want to tie up a single thread and not listen to the ethernet port for too long.  It is possible (and even likely) that while I'm sending data out the serial port additional commands will come in the ethernet port.

I could use an event, however if the serial link is busy and/or multiple events come in, the serial thread will not know it.  A counting semaphore might be possible to keep track that there are more things for the serial link thread to perform...? A queue of some sort is needed so the ethernet listening thread can load it while the other is busy.

Any other comments or suggestions would be appreciated.

Thanks.
0
pgnatyukCommented:
1. Implement this queue yourself.
2. Try to use boost. It's a kind of a fashion now, but seems like this is exactly what you need.

BTW,
MSDN. Message Queuing (MSMQ)
http://msdn.microsoft.com/en-us/library/ms711472(VS.85).aspx
0
jkrCommented:
I'd recommend thinking about using 'PostThreadMessage()' together 'GlobalAlloc()'. This way, the data chinks will be placed in the receiving thread's message queue where you can process them one after one. I.e.
#define WM_DATAREADY (WM_USER + 0)

// thread on ethernet port

LPVOID pv = GlobalAlloc(GPTR,BUF_SIZE);

recv(s,(char*)pv,BUF_SIZE,0);

PostThreadMessage(nSerialThread,WM_DATAREADY,0,(LPARAM)pv);


// thread on serial port

MSG msg;

while(GetMessage(&msg,NULL,0,0)) {

  if(WM_DATAREADY == msg.message) {

    LPVOID pv = (LPVOID) msg.lParam;

    SendToSerialPort(pv);

    GlobalFree(pv);
  }
}

Open in new window

0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
JohnSantaFeAuthor Commented:
JKR,

Will the thread suspend when using GetMessage()  ?
If not, would using WaitMessage() followed by GetMessage() make sense so the thread isn't constantly spinning?
0
jkrCommented:
The thread will be suspended, as 'GetMessage()' is a blocking call and will not return until at least one message is received, see http://msdn.microsoft.com/en-us/library/ms644936%28VS.85%29.aspx ("GetMessage")
0
JohnSantaFeAuthor Commented:
Thanks the wording in the MSDN article was a little unclear to me.
I'll give this a try and post back later.
0
ambienceCommented:
Check POCO library, it has pretty decent NotificationQueu and NotificationCenter classes that will do exactly what you want to in a portable manner.
0
ambienceCommented:
Oh and it also has SocketReactor pattern implemented so that would be another useful goodie.
0
ambienceCommented:
Sorry for multiple comments, but im a dizzy at the moment.
http://pocoproject.org/docs/Poco.NotificationCenter.html 
0
JohnSantaFeAuthor Commented:
I decided to go with JKR's suggestion of using PostThreadMessage and GetMessage.  

The libraries, especially Poco look pretty interesting, but for now I just want something simple.

Thanks for the help.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
C

From novice to tech pro — start learning today.