At last I have managed to come up with a dead easy to use inter process communication library. This awesome (if only you knew what was going on behind the scenes) library lets one Basic4ppc client application call the Subs of another Basic4ppc server application on the same computer, over a network or even over the Internet!
It is based on two technologies. The .NET Remoting facility that is built in to the .NET Framework and the Caller code from my Basic4ppc debug suite http://www.b4x.com/forum/additional...-legacy-optimised-applications.html#post27120
Unfortunately this will only work on the desktop as the Compact Framework does not support Remoting although there are a couple of third-party implementations that I may investigate - cost permitting.
As usual library, source, help and deceptively simple demo applications are included.
EDIT: As a clarification. An application is not restricted to a single RemoteObject. So, for example, a pair of comunicating apps could each have two RemoteObjects on different ports and with different remote service names, one a client to the other app and one a server to it. This would enable two-way calling of each others Subs. Things could get a bit confusing though if you aren't careful!
EDIT:- Version 1.1 now posted includes a RemotingCF library that will work on devices and between desktops and devices. See post #10 for details.
EDIT:- Version 2.0 for Basic4ppc v6.90 and later now posted. See post #13 for details.
It is based on two technologies. The .NET Remoting facility that is built in to the .NET Framework and the Caller code from my Basic4ppc debug suite http://www.b4x.com/forum/additional...-legacy-optimised-applications.html#post27120
Unfortunately this will only work on the desktop as the Compact Framework does not support Remoting although there are a couple of third-party implementations that I may investigate - cost permitting.
As usual library, source, help and deceptively simple demo applications are included.
EDIT: As a clarification. An application is not restricted to a single RemoteObject. So, for example, a pair of comunicating apps could each have two RemoteObjects on different ports and with different remote service names, one a client to the other app and one a server to it. This would enable two-way calling of each others Subs. Things could get a bit confusing though if you aren't careful!
EDIT:- Version 1.1 now posted includes a RemotingCF library that will work on devices and between desktops and devices. See post #10 for details.
EDIT:- Version 2.0 for Basic4ppc v6.90 and later now posted. See post #13 for details.
Attachments
Last edited: