Overlapped Named Pipe IPC

[Nine]

From this this thread, I started to get interested in very fast communication that could be used between VBS or AutoIt.  And thanks to @argumentum, he is always there to challenge any IPC solution .

My last tests show that a request from a dedicated client is about 7ms to transit to the server.  And a small response takes about 4ms to be sent from the server to the client.

From a basic snippet, I changed it to make a UDF on request from the community of @mLipok .  Now with this UDF, you can create duplex communication but also dual channels (one way to) IPC.  You can also make it persistent (close to a Peer-to-Peer approach) or a transactional (more of a client-server protocol).

Example 1 :  Duplex and persistent

Example 2 : Dual and persistent (VBS example included)

Example 3 : Duplex and transactional

Whether you find it useful or not, your comments are always welcome ! (former is my preference though)

Version 2022-02-11

* Added security descriptor to allow mix elevation between Client and Server

* Added support for IPC between computers

Version : 2020-12-30

* Added documentation to the UDF file

* Optimized code

* Moved some code from Example files into UDF file

 

 

NPIPC UDF.zip

Edited February 11, 2022 by Nine

[mLipok]

@Nine please combine functions from both snippet to one UDF file, and use unique names which will not interfere with other UDF's possible functions.

Then your work became quite nice UDF.

 

[water]

BTW: Could you please fix the typo in the thread title? So people can find your code when searching for "named pipe"

Edit: Done - M23

Edited December 28, 2020 by Melba23

[Nine]

On 12/28/2020 at 4:39 AM, mLipok said:

please combine functions from both snippet to one UDF file, and use unique names which will not interfere with other UDF's possible functions.

Alright, it is done.  

[Nine]

New version available 

ps. Uploaded new version moments ago...

Edited December 31, 2020 by Nine

[Nine]

New version available