Sharing the goodness…
Beth Massi is a Senior Program Manager on the Visual Studio team at Microsoft and a community champion for .NET developers. Learn more about Beth.
More videos »
There's a new article up on the VB Dev Center by Rob Windsor, a follow up from his first Getting Started with WCF article, called Using Custom Business Objects with Windows Communication Foundation. Rob explains how to serialize your own custom business objects using WCF DataContracts and what issues you may run into in Visual Studio 2005. Check it out!
PingBack from http://msdnrss.thecoderblogs.com/2007/11/02/new-community-article-using-business-objects-with-wcf/
I have read both the articles on WCF. WCF undoubtedly promises to be great technology. But I have questions on how it addresses issues faced in "old" (COM+)times. We had a 3 tier web-based application and users spread across the globe from US to Australia. Most of the issues we faced were due to network bandwidth limitations. Our infrastructure team always used to say/(s) that "no matter what you do, the speed of processing will always be dependent on n/w b/w". We had 1 COM+ server which used to be accessed by ASP pages and that COM+ server used to do talking with database server to cater data to ASP pages. The servers (COM+/SQL Server) were located in UK. Users,especially from Australia, always used to complaint of slow performance. Network team diagnosed the problem to be the "distance" between AU and UK fot it. They also suggested to have "regional" COM+ servers.
i.e 1 COM+ server for UA,another for EU and another for APAC. At that time the deployment of COM components made this option impossible. I want to know, with WCF, how can this problem be addressed?
First off, WCF will not solve the issue of sending data across the network, that will always be a bottleneck. There are things you can do to help - like using a binary or MTOM encoding or streaming - but they will not completely solve the problem.
Now, to your last question, deployment of a WCF service is no different than deployment of a web site. You just need to create a virtual directory on a web server and copy up your svc file, web.config, and assemblies with your contracts and services. You also have to make sure access to the server is properly configured but that's more of an infrastructure issue than a deployment issue.
Also I would like to ask is how different is Binary Serialization from DataContract? I'm really interested how datacontract works perhaps you can give me a headstart by explaining what is datacontract and what are the advantages and disadvantages of it? Also, if you can explain how would it make the BO Serialization more effecient.
Thanks a lot,