I believe you mean Windows Communication Foundation aka Indigo.
Windows Presentation Foundation aka avalon is the new graphics
subsystem.
Going forward, I would lean more towards the .NET remoting solution
over the webservice approach. I have listed several reasons below:
- .NET Remoting is faster and better optimized over webservices
(Today)
- .NET Remoting will provide an easier route forward, regardless of
whether you switch to Webservices or stick with the higher performing
binary protocol.
- Webservices might not provide an easy way forward.
..NET remoting is straight up faster and more efficient than
webservices. This is true of today anyways. Who knows in the future,
with the speed of webservices coming in leaps and bounds.
Under Indigo, the only difference between a WebService service and a
Indigo Service is a change of configuration files. If you have a .NET
indigo service and later decide to switch it over to a webservice type
application it should be as easy as a config file switch.
If you properly design today for a Remoting Application (following the
interface recommended approach), then the migration path forward for
WCF/Indigo services will be clearer and have more support. Here is a
page talking about the future of .NET remoting.
http://blogs.msdn.com/richardt/archi.../05/84771.aspx
Webservices may not provide such a supported or easy way forward, then
again, it may as well. Time will tell.
Cheers,
Adam Cooper
-------------------------------------------------------------------------------------------
J-Integra Interoperability Solutions
http://j-integra.intrinsyc.com/
java, corba, com & .net interoperability middleware