 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
.NET Forum / .NET Framework / Distributed Applications / March 2006Remoting vs WebServices - Microsoft recommendation for web based apps...
I have spent the last few weeks trawling blogs, newsgroups, MSDN articles etc etc trying to make some decisions for a large scale application I am undertaking which will be internet based but using a SmartClient type Win Forms client. Im trying to decide on my architecure... I have been thrashing around between DataSets vs Custom Entities, Remoting vs Web Services amongst others. I just spotted this... http://msdn2.microsoft.com/en-us/library/8119f66k(VS.80).aspx Where it states...(discussing Remoting vs Web services) "Because it is not recommended to use remote objects across the Internet, there are now few scenarios that require HttpChannel. If you must communicate across the Internet, it is recommended that you use ASP.NET to create XML Web services." If this is true then my decision is made surely? But why are so many ORM frameworks out there still offering remoting type solutions, even those aimed at creating SmartClient apps (Ideablade for instance) if this is Microsofts own recommendation ? Im interested in anyones views on this, cheers Chaz Chaz, | If this is true then my decision is made surely? But why are so many ORM | frameworks out there still offering remoting type solutions, even those | aimed at creating SmartClient apps (Ideablade for instance) if this is | Microsofts own recommendation ? Because you would be using them in an Intranet (inside firewall) type application. When deciding between Remoting or Web service I tend to look at where the application lives. If the app is entirely within the Intranet then I would lean toward Remoting, if the app needed to be outside the firewall (the "Internet") then I would use Web Services. I would consider web services for an intranet application if any of the "clients" required it, for example if Office or InfoPath was a client of the service (as oppose to only my developed client)... Choosing DataSets vs Custom Entities is an entirely different choice. If the "data" has logic/behavior to it I would favor custom entities, if the "data" has no real logic/behavior  SignatureHope this helps Jay [MVP - Outlook] .NET Application Architect, Enthusiast, & Evangelist T.S. Bradley - http://www.tsbradley.net |I have spent the last few weeks trawling blogs, newsgroups, MSDN articles | etc etc trying to make some decisions for a large scale application I am [quoted text clipped - 19 lines] | | Chaz Ok, very interesting, thanyou for your points of view On the Custom Entities vs Dataset front for me I think it has to be Custom Entities, but Im having a lot of touble deciding the best transport pattern. Serialization (Binary or XML) serilization of my custom entity class seems good, but all collections must be sent as Arrays, I was hoping to Binary Serialize a DataTable and re-serialze it at the client and use it as the underlying source for an Entity Collection, thus maintaining proper DataRow information (where each DataRow represents an Entity) - but any serializing around DataRows or DataTables seems frought with complication, whereas Custome Entity serialization can be done in minutes. So the juries still undecided on that one, thanks again Chaz > Chaz, > | If this is true then my decision is made surely? But why are so many [quoted text clipped - 47 lines] > | > | Chaz Hi Chaz, A good book for you to read is Enterprise patterns by Martin Fowller. He talks about how do design your application. There are tow good options as you know. First one is Domain model and the second is Table model. Let me explain. The Domain model uses objects, OOP and ect to define you application by, while Table model uses dataTables and dataSets. The thing is that microsoft recomends us to use Table model, because the .NET framework is based on that. However, it is very hard for me to not use real OOP design. My first choice is always the Domain model, but you should always keep in mind that microsoft gave us a powerfull Table model capabilities. Hope this helps. > Ok, very interesting, thanyou for your points of view > [quoted text clipped - 64 lines] > > | > > | Chaz 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.