hhblaze/sharmipc

IPC [inter-process communication] engine for .NET based on memory-mapped files.

sharmipc's Issues

Issues when creating many new instances quickly

I have a simple app that spins up 100 processes as test and tests some messages going back and forth as i was building it up to test concurrency before i integrate the wrapper around SharmIPC i build to auto serialize and deserialise my classes as well as manage all the processes.

What i found is that if i spin up a lot of processes instantly a large number will of the SharmIPC Slaves will fail to send the first message i try to send. This message is a hartbeat and notification the child process has started so if it fails my child process shuts down. Interesting thing i found is the more i delay the start up of each new process the more child processes work successfully. For example at a 1 second delay 50/100 will start and send first message without error but at 2 second delay then 75/100 will start successfully and send first message.

Is there any know limits here? I can see the messages that the master and slave have started in console even though there is no way to check it on the IPC instance itself. All i get back the the false for it failing to send and it does not arrive on the receiving side.

Debugging has not helped too much yet and i need to find a way to get the actual error.

I can't say for sure it is not Anti virus or something on my computer causing this but thought i would check first if i am hitting some known issue.

the document and sample code need enhance

i'm wondering how can such bad sample code get so many starts?

lose package or wrong order

I have two process, A send package, B receive package.
I use RemoteRequestWithoutResponse function to send package.
(a package is 389 byte)
The issue is, it lost some package or wrong order sometimes.
(both of 1.16 and 1.17 )

Does this work on Mono?

I could not get this project to work correctly under Mono, please can you confirm that this works on Mono? I am testing under Mono 4.2.1 using Ubuntu 16.04 LTS.

The Mutex, as implemented on Mono does not provide the same inter-process synchronization like it does on Windows going back as far as version 2.8.0.

UWP really supported

Are you sure UWP is really supported? I just tried it, did no work, and the documentation says Memory Mapped files are currently not supported by UWP:
MicrosoftDocs/windows-dev-docs#458

Missing eProtocolVersion

Hi, this looks like a VERY nice package, thank you.
When I install from Nuget, the latest 1.16.0, and try to do the new() in your examples, tiesky.com.SharmIpc.eProtocolVersion is not recognized and gives a compile error. When I instead reference your SharmIpc.dll directly (SharmIpc462, built from git clone) the enum is recognized, no build issues.
Best regards,
Dale

SharmIPC not working within a service

Hello,

to me it looks like SharmIPC won't work when the implementation is run as a service. I usually have a project with the implementation, accompanied by a console project (for testing) and the service project. Normally the first started console project registers as a MASTER and the second console project as a SLAVE. When running these projects as a service they don't seem to know each other. Both of them register as MASTER and they can't communicate. Is there any solution to this?

SharmIPC with strong name signing

Could you release a strong name signing version on nuget?
Thanks.