What web services / interface to use?

We are developing a system with C / C ++ backend server and C # .NET front end. We would like to provide a web interface similar to the C # .NET interface. Can you suggest a better way to do this? eg Do I embed a web server in a backend server? How do I get the maximum common code between .NET and the web to minimize maintenance, etc. Thanks in advance!

0


source to share


1 answer


Depending on the needs of your application, it might be better to just disable the C # client and create a web interface. This way, your customers can save money without buying a .NET Windows box — a browser is all you need. You will also be able to update your site and get all the benefits from your customers instantly.



But if you choose to build both, there are several paths to choose from. You can place your business logic very close to the server. You can even write it in C ++. Then use a common communication layer and separate presentation layers for each of your client applications (web and desktop).
Another approach is to bring the business logic closer to the customer. Write it in .Net and include it in your desktop app and website. This business application can communicate with the back-end server using some abstract strategy (soap for the desktop client and direct for the web server). Of course, that doesn't save you from writing validation code on your original C ++ server.

+1


source







All Articles