This is a very general question - I'm hoping for some references to articles or projects that are applicable to what I'm trying to do, not specific answers. (I've had very positive experiences previously here at MSDN forums, inspiring me to ask this question.)

I want to make some kind of "distributed object system" (DOS?) with the following characteristics:

- the system consists of various processes, some running on separate PCs (clients), some running on servers, often several different server-style processes running on the same server, all machines with network connectivity to each other

- some processes create objects and some consume them, and there will be one caching dispatcher style process that acts as a hub

- objects are moved around with serialization and deserialization, and with TCP/IP or named pipes, depending on whether any two processes are on the same machine or not

- so the topology is multi-tier client-server (is that the correct designation?) and based on using objects instead of sending and receiving messages

Also to be taken into consideration is that I want to do this myself - I've already created my own serialization/deserialization and my own TCP/IP and named pipes communications layers and my own multi-threading support, all in C#. In other words, my own poor-man's Remoting.

So, any suggested articles, projects, discussions that would help me in final design and implementation?

Is this the correct forum to ask about this? I tried in the Architecture forum and got zero replies...

Thanks in advance.

Rennie

Hi Rennie,

So, if you have all of the remoting complete, what else are you lacking? I am afraid I don't understand what is left on your project, so others might have the same question.

I came across this because I have a similar question that I just posted *with code*. It might help you, but I'm hoping more that you might be able to help with my problem, too:

Link http://social.msdn.microsoft.com/Forums/en-US/netfxremoting/thread/1fd0d0f4-3d76-4d08-bb94-5312b3b3caed

I look forward to hearing from you soon,
~Joe

Thanks for your reply, Joe.

What I'm hoping for is some references to articles or projects of the "we've done this and here's how we did it" nature.

Otherwise I'm afraid that I'll do it all on my own, and then when I'm done I'll suddenly discover I had forgotten to take some key problem into account, and I'll be cursing, "oh *?/%, if only I'd thought of that before!"

Qustions like, should a new version of an object automatically be pushed around the system to replace previous versions of that object, and how to indicate that an object is no longer valid and should be purged from the system, and is there a simple and efficient way to persist objects without needing afull-blown database system, and should large objects (containing images) be treated completely differently from small objects, etc. etc.

Rennie