Inter Process Communication/Remoting library

[agraham]

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.basic4ppc.com/forum/addit...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.

[derez]

Andrew
This is beautiful, and I don't want to know what is going on behind the scenes...

I see a mountain of games for two players, using exactly the same code, where each player does his move on his application and his opponents application, without messages.

Thanks

[Erel]

Thank you once again for your magnificent creations

[Mr_Gee]

Brilliant!

[Ariel_Z]

Brilliant.

[derez]

Andrew
Playing with this library, I managed to connect on my home lan, using TCP and the host name, but not when using the host internal IP :

This works - Remote.connect("Tcp" , "main" , 51234 , "Remote")
and this doesn't - Remote.connect("Tcp" , "192.168.0.167" , 51234 , "Remote")

In the second case I get this error:

"Remote.CallGuiSub("Launch",par())
Error description:
Server encountered an internal error. For more information, turn off customerrors in the server's.config file"

What am I doing wrong ?

[agraham]

Originally Posted by derez

and this doesn't - Remote.connect("Tcp" , "192.168.0.167" , 51234 , "Remote")

At the moment it only accepts host names not IP addresses, the next version will.

In the second case I get this error ... What am I doing wrong ?

I'm afraid that I don't know! Is that on the client or server? Is it locally or over the network. If it works if you call that on the server oor locally on the client it will most likely be a network problem of some sort.

[derez]

At the moment it only accepts host names not IP addresses, the next version will.

I followed the help file which says:

The hostname is only used by the client to locate the computer where the server is located and may be a dotted quad IP address or the domain name of the computer

This explains the problem, Thank you.

[agraham]

Originally Posted by derez

I followed the help file which says:

Sorry. Yet another cut and past oversight ,

[agraham]

Version 1.1 includes a RemotingCF library that will work on devices as well as desktop. It uses a home grown (i.e.crude!) remoting layer based on TCP. Details in the help.

It is now an error to call an Async method while another is pending and an Exception is thrown if this is attempted.

Dotted quad IP addresses as well as hostnames may now be used.

Async data calls are now provided and all Async calls have a tag parameter that may be retrieved in the AsyncEvent and used to identify what to do.

A sample application for RemotingCF is provided to show that two way calling is possible.

Enjoy .