My company makes smart electric meters and I have written programs for monitoring them and doing tenant billing. We recently received an inquiry from a company that sells marina management software wanting to know if we could provide them a meter interface they could talk to with Active-X. Since Xojo can’t do Active-X as a host, I am looking at alternatives. An IPC socket looks like the best way for two programs on the same computer to communicate with each other, but after quick scan on the net, I did not find any Windows support for this method. A TCP socket looks like overkill so I am thinking a UDP socket may be the answer. I would like to hear from someone who has experience with communicating with .NET programs.
Windows doesn’t really support IPC SOCKETS so an IPC socket on Windows won’t work between anything but 2 Xojo applications.
TCP or UDP could work
[edited to clarify that this is IPC SOCKETS - not IPC in general]
[quote=53833:@Norman Palardy]Windows doesn’t really support IPC so an IPC socket on Windows won’t work between anything but 2 Xojo applications.
TCP or UDP could work[/quote]
ehmm
http://msdn.microsoft.com/en-us/library/windows/desktop/aa365574(v=vs.85).aspx
[quote=53834:@Derk Jochems]ehmm
http://msdn.microsoft.com/en-us/library/windows/desktop/aa365574(v=vs.85).aspx[/quote]
Since we’re talking about Xojo & IPC Sockets in Xojo - not ipc in general -
IPC sockets on Windows won’t work between anything but 2 Xojo applications.
TCP or UDP could work
The rest of the schemes on Windows are not available using an IPC SOCKET - but you might be able to use declares to get at them
Thanks guys. I was afraid that was going to be the answer.
Perhaps a named pipe would be the answer? I built a Xojo component to do this - you can get it here.
You might be able to use Xojo declare.
See attached link when used with Visual basic: http://www.codeproject.com/Articles/3815/Inter-process-communication-using-registered-messa