When does one use .NET Remoting/ Web Services to communicate within a distributed application?
The typical text book guiding rules say that .NET Remoting should be use when both ends of the application are running on MS systems. .NET Remoting is better than WS because it's faster due to binary serialisation.
Well, Nick Weinholt thought otherwise, particularly with WSE 2.0 and with Indigo forcoming with the release of Longhorn. This topic was discussed during the recent MDNUG (Melbourne .NET User Group) meeting (23/11) and was blogged by Chris Hewitt from Readify.
There are some interesting points raised in the summary. I strongly urge you esp those of us who are developed enterprise or distributed applications to read it before jumping into remoting.
Appendix
1. ANZ DEC Update: MSDN WSE 2.0 with Nick Wienholt
WSE 2.0 represents a significant advance for web service developers. By supporting the creation of web services the implement industry standards like WS-Security and WS- SecureConversation without delving deeply into code or configuration files, WSE cuts down the amount of time developers need to spend addressing plumbing issues, and allows them to concentrate on solving their business issues.
This presentation will cover
What are the WS-* specifications, and how do they make development simpler?
Where does WSE2 fit into the Microsoft messaging product line, and when should I use it (and when should I avoid it)?
Building a secure web service using WSE2.
An overview of the other functionality that WSE offers.
Calendar of events
02 Dec 18:00 Sydney Deep .NET, AU
06 Dec 18:00 Auckland, NZ
07 Dec 11.00 Christchurch, NZ
07 Dec 18.00 Wellington, NZ
08 Dec 18.00 Adelaide, AU
09 Dec 18.00 Wollongong, AU
13 Dec 08.00 Perth, AU
14 Dec 18.00 Brisbane, AU
15 Dec 18.00 Gold Coast, AU
16 Dec 16.30 Canberra, AU
About the presenter
Nick Wienholt is an independent Windows and .NET consultant based in Sydney. He is the author of Maximizing .NET Performance from Apress, and specialises in system-level software architecture and development, with a particular focus of performance, security, interoperability and debugging.
2. Indigo is a set of .NET technologies for building and running connected systems. It is a new breed of communications infrastructure built around the Web services architecture.