Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.
COM port simulation: Named Pipes
I do not have 2 COM ports on the back of my PC, so I am trying to use an internal software pretend comport.
I am trying to use Named Pipes, as I require bidirectional FIFO comms. However, the examples I have seen all depend on knowing whether you are programming the client or server end of the pipe.. i.e. server: CreateNamedPipe().... Client: ConnectNamedPipe()...
I am trying to encapsulate this in a class so I can use the same code in both client and server ends... which ever end starts first will create the pipe, and which ever is last out will close the pipe. (hopefully, windows is clever enough to know that when I CloseHandle() the last one out will destroy the resources??? )
Any Ideas please???
Thanks.
Nigel.
I am trying to use Named Pipes, as I require bidirectional FIFO comms. However, the examples I have seen all depend on knowing whether you are programming the client or server end of the pipe.. i.e. server: CreateNamedPipe().... Client: ConnectNamedPipe()...
I am trying to encapsulate this in a class so I can use the same code in both client and server ends... which ever end starts first will create the pipe, and which ever is last out will close the pipe. (hopefully, windows is clever enough to know that when I CloseHandle() the last one out will destroy the resources??? )
Any Ideas please???
Thanks.
Nigel.
Who is Participating?
THis article contains cod that creates a CNamedPipe class, derived from CFile. It should answer all of your questions.
Garden Hoses at Work
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnpic/html/msdn_npipes.asp
A quick read indicates that the author does *not* expect to make the ends of the pipe interchangeable. One end is the server and one is the client. But remember that communication is bidirectional, so it doesn't really matter which end is which once the connection is established.
-- Dan
Garden Hoses at Work
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnpic/html/msdn_npipes.asp
A quick read indicates that the author does *not* expect to make the ends of the pipe interchangeable. One end is the server and one is the client. But remember that communication is bidirectional, so it doesn't really matter which end is which once the connection is established.
-- Dan
You can't make the ends interchangeable.
The closest you can do is to make your client continuously try to connect to a server.
The closest you can do is to make your client continuously try to connect to a server.
Sorry for not getting back for a bit, but been doing lots of other things...
If you test to see if the pipe exists first you can either attach to it if it exists, or create it if it doesn't. That way you can make the same class handle the work, and you don't have to worry about the concept of server/client.
When you close the hanldes, Windows handles the cleanup, so the server can disconnect first, and the pipe can still be connected to by another process.
If you test to see if the pipe exists first you can either attach to it if it exists, or create it if it doesn't. That way you can make the same class handle the work, and you don't have to worry about the concept of server/client.
When you close the hanldes, Windows handles the cleanup, so the server can disconnect first, and the pipe can still be connected to by another process.
Question has a verified solution.
Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.
Have a better answer? Share it in a comment.
All Courses
From novice to tech pro — start learning today.
-
Course of the Month6 days, 14 hours left to enrollMonitoring and Operating a Private Cloud with System Center 2012 R2 273 lessons
DarthMod
Community Support Moderator
Experts-Exchange