Distributed Application Logic

[Chris Smith]

Experienced posters,

Got a design type of question for you (using vb.net).

Thinking of a way to implement a group of process client apps, Each of these
executables, will run on different node on a LAN, and a couple across the
internet. I would like them to start up and connect to a "server" to get
data to be worked on and then return the resulting object. Some of the data
will be cached locally on the client processor for logic reasons, but that
data can be updated on any client at any time and will need to be propagated
to the other nodes for use in future processes. If you thing P2P you will
have the idea that I am shooting for, once one of the node has a complete
object loaded, any node should be able to load the object at any time, as
well as updates or complete updated object.

What is the fastest method of doing this? Fastest meaning that update of
updated data across nodes.

Thanks for ideas.

Chris

 

[MS public]

You might want to consider using a web service(s). Soap may be what you
need.

Regards - OHM

 

[Cor]

Hi Chris,

Have a look at this very fine walkthrough, still one of the best in my
opinion.

http://msdn.microsoft.com/library/d...atingdistributedwebapplicationwalkthrough.asp

Cor

 

[Cor]

Hi Chris,

Forgot to mention it, like the advice from OHM, this is a webservice
solution.

Cor

 

[Chris Smith]

Thanks for the recommendations, but unfortunately web services cannot be
applied as the use of a web server cannot be used in this application.
(Darn Requirements)