Hi Sitt, We have a setup in our company that sounds similar to what you describe. We have a very simple approach that works very nicely. Our client application contains code to create xml files, and other code that can read xml files. Same thing for the server application. When the server app does something that should influence whatever happens on the client machines, it creates an xml file with the necessary data, and copies it to a shared or ftp folder. The client app checks this folder on a regular basis, and when it finds an xml file it reads it, and does something with the data. When the client app does something that should influence the server, it creates an xml file of its own and puts it in the same (or another) shared folder. The server also checks the folder on a regular basis, etc. This process is very easy to secure, and to create, but it is not very good if you need to have very fast traffic between clients and server. Hope this helps you, Johan
