How to change my application (Client-Server using TCP/IP Sockets) to internet based application
-
We have an application developed using MFC in Visual Studio 6.0. which is a client-server based architecture using TCP/IP Sockets. The server application reads data from text files and binary (which acts as database). Based on the Network configuration, the client application that runs in various stations (PCs connected within the LAN Network) connects to the Server application. Exchange of data then takes place between the server and various number of clients that are connected to the server. All the communication happens using the TCP/IP socket protocol. Now there is a requirement to convert the existing architecture to web based architechture such that the Server is installed in a remote PC. The clients from various geographical locations have to be connected to the Server. Please provide me guidelines how to convert the existing architecture to web based architecture.
-
We have an application developed using MFC in Visual Studio 6.0. which is a client-server based architecture using TCP/IP Sockets. The server application reads data from text files and binary (which acts as database). Based on the Network configuration, the client application that runs in various stations (PCs connected within the LAN Network) connects to the Server application. Exchange of data then takes place between the server and various number of clients that are connected to the server. All the communication happens using the TCP/IP socket protocol. Now there is a requirement to convert the existing architecture to web based architechture such that the Server is installed in a remote PC. The clients from various geographical locations have to be connected to the Server. Please provide me guidelines how to convert the existing architecture to web based architecture.
You need to convert your server into a web server using one of the web architectures available. If you are familiar with Microsoft products then ASP.NET[^] would be a good choice.
Unrequited desire is character building. OriginalGriff I'm sitting here giving you a standing ovation - Len Goodman
-
We have an application developed using MFC in Visual Studio 6.0. which is a client-server based architecture using TCP/IP Sockets. The server application reads data from text files and binary (which acts as database). Based on the Network configuration, the client application that runs in various stations (PCs connected within the LAN Network) connects to the Server application. Exchange of data then takes place between the server and various number of clients that are connected to the server. All the communication happens using the TCP/IP socket protocol. Now there is a requirement to convert the existing architecture to web based architechture such that the Server is installed in a remote PC. The clients from various geographical locations have to be connected to the Server. Please provide me guidelines how to convert the existing architecture to web based architecture.
Hi, First you need to convert your Server portion to a web architecture.You can use ASP.Net and SQL Server. Then develop the client in Visual c++ or something else, the client must communicate to the database.
-
We have an application developed using MFC in Visual Studio 6.0. which is a client-server based architecture using TCP/IP Sockets. The server application reads data from text files and binary (which acts as database). Based on the Network configuration, the client application that runs in various stations (PCs connected within the LAN Network) connects to the Server application. Exchange of data then takes place between the server and various number of clients that are connected to the server. All the communication happens using the TCP/IP socket protocol. Now there is a requirement to convert the existing architecture to web based architechture such that the Server is installed in a remote PC. The clients from various geographical locations have to be connected to the Server. Please provide me guidelines how to convert the existing architecture to web based architecture.
"How to change my app from using Internet Protocol, to an Internet based one" Er, anyone else see a problem here?
manoharbalu wrote:
Now there is a requirement to convert the existing architecture to web based architechture
So you can market it as 'Cloud' no doubt? Just leave it as it is, it is already an internet based app and slap 'Cloud' on the box to fool the muppets and marketing types who use words without understanding what they mean. :)
============================== Nothing to say.
-
We have an application developed using MFC in Visual Studio 6.0. which is a client-server based architecture using TCP/IP Sockets. The server application reads data from text files and binary (which acts as database). Based on the Network configuration, the client application that runs in various stations (PCs connected within the LAN Network) connects to the Server application. Exchange of data then takes place between the server and various number of clients that are connected to the server. All the communication happens using the TCP/IP socket protocol. Now there is a requirement to convert the existing architecture to web based architechture such that the Server is installed in a remote PC. The clients from various geographical locations have to be connected to the Server. Please provide me guidelines how to convert the existing architecture to web based architecture.
The internet is based on TCP so at the basic level there is no difference. The two factors that are relevant. 1. You must have a public IP. On a lan you probably have a private one. The public IP allows someone on the internet to address you. You might, but it is not required, also want to have a Domain Name. There will probably also need to be seem network infrastructure setup to route from the public facing hardware to the actual server. None of this has anything to do with the existing server/client code unless the client code does not allow a way to specify an IP/Domain Name (because someone hardcoded the IP.) 2. You MUST provide security. User/pwd should be sufficient as long as the pwd strength is sufficient. You might already have that in the code but if not it must be added. Besides the above you might want to investigate SSL depending on the nature of the data that gets sent.