|I had a previous post regarding how to design a socket based client-server system with C#.net which will scale very well. http://www.codeproject.com/script/comments/forums.asp?msg=913692&forumid=1649#xx913692xx[^]
Heath gave a very interesting response, which told me:
(1) Use Web Services or .net remoting to free yourself from the socket level details
(2) Try to use WSE DIME for file transfers
I am reading on these.
A further question in this context:
I have observed that many clients do not allow incoming http connections inside their firewall. They typically have the DMZ firewall configuration. The Web Server will be in the DMZ and app servers will be inside. They also do not permit to have their business logic sitting on the IIS machine.
So even though I have a Web service based entry to my system, it still has to do socket communication with my server sitting inside the firewall over an admin allowed port.
<->DMZ<-> [Allows only http]
Web Service (IIS)
<->Firewall<-> [Allows only my chosen port]
My Server (With DB/NTFS/Network access)
Am I missing something? Are there any better options?