Good Client/Server Tutorial?

[ryan]

Hi guys I'm running in an architecture issue. I'm trying to figure out how to get past a little issue I'm working with. To make this simple I'll try to explain it simple.

Situation:
I'm trying to build a main (server) application that will run on one machine. This main (server) application will need to be able to 'talk' (invoke commands) on other systems within it's network and then pass very simple information back (successfull or not, time stamp, little things).

What I'm trying to figure out is how I should create the main (server) application and the client (server) application. The need of the server program will be the gateway and distribute the tasks to the other 'client' servers on the network. So the client programs will be the ones carrying the tasks out on its own system but the main server application will just be managing things like logging and passing the information back to the user via the web. I do know that my service server application will need an API so that my ASP pages can invoke public functions.

Question:
Should this main (server) application be written using COM/DCOM technology or something using WinSock or something else that runs based on ports. In addition does anyone have any recommendations, or questions that I can answer, or sites that offer a good client/server tutorial.

Any ideas, do I need to elaborate on something else for clearification?

Thanks!

 

[Cagliostro]

Is up to you. I think better is to use a SQLServer, and all the applications(ASP,COM/DCOM/ActiveX,CGI based and other applications) to be oriented to it. John Fill