 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
.NET Forum / Windows Forms / Design Time / April 2005Achitecture question
Hi I have a Windows Form running in 40 clients around the city, those apps are communicating with a central SQLDB hosted in a hosting company (each one is sending data, waiting for data comparisons and receiving the data back). I have been using a Web Service to make the link between my apps and the SQLDB, but now I want to connect my Windows Form apps directly to de SQLServer (because I think the roundtrip is going to be faster, which is the most important factor in my app) My question to the architects and everyone: Is this a good, secure, recommended, intelligent practice or this is a big big mistake ?? thks ken First of all, this is not the architect's newsgroup, designtime here refers to design-time feature of visual studio. About your question, although I am not an architect myself, I think eliminating the webservice component of your application opens security holes in your design which is what a webservice is for. Having your client app connect directly to your sqlserver means that the clientapp will have to know where to connect to (instance of sql server), knowing the location of such can open vulnerabilities to your data. Perhaps you just need to optimize the queries used in processing data.  SignatureJoey Calisay http://spaces.msn.com/members/joeycalisay/ > Hi > [quoted text clipped - 14 lines] > > ken > opens security > holes in your design which is what a webservice is for Well said! =) ROFL > First of all, this is not the architect's newsgroup, designtime here > refers [quoted text clipped - 33 lines] >> >> ken I'm sorry but I just get that from the books I've read, if there is something wrong with that, you can comment about it and perhaps help us. I don't get what you are laughing about. Thanks. SignatureJoey Calisay http://spaces.msn.com/members/joeycalisay/ > > opens security > > holes in your design which is what a webservice is for [quoted text clipped - 38 lines] > >> > >> ken Web services can be used as a façade layer to hide the complexity of the business/data logic, meaning that in this façade you only expose the methods that you want to expose. There is no doubt about wether to use Web Services or not if one of the requirements is the interoperability of heterogeneous systems. If you know that all the layers will be CLR managed you should opt to use .NET Remoting but know that .NET Remoting objects can also be hosted in IIS as Web Services. To answer Kenny's question: there is nothing wrong with using the 2-tier architecture for a small app but know that there are a lot more disadventages than advantages using this approach. The biggest disadventage is the maintainability and the scalability and the biggest advantage (time-saving) can also become a disadventage and I talking about the time it takes to develop the application. I for like 99% that in the near future you are going to add functionality so you should really consider using at least the 3-tier model. It all depends on the project, the requirements, budget, ... Gabriel Lozano-Morán > I'm sorry but I just get that from the books I've read, if there is > something wrong with that, you can comment about it and perhaps help us. I [quoted text clipped - 56 lines] > > >> > > >> ken Free MagazinesGet these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...
|
Reply to this Message
|
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.