InterprocessConnectionServer with named pipe


#1

Hi Guys,

I would like to know if there are technical restriction leading to the fact
that there is no InterprocessConnectionServer using juce::NamedPipe ?

I’m currently using the socket version but find annoying to have to authorize my app in the Windows firewall even if I only want a local communication.

After some digging it seems that NamedPipe do not have something like waitForNextConnection. It this impossible or does it just lack a proper implementation ?

Thanks,


#2

It could probably be wrapped in some way to make it work like that… I’ve never looked at it with a view to doing that though…