> There's a great article in the newest CoDe magazine that says
> Enterprise Services offers better performance than both Remoting or Web
> Services, and it has a better future migration path to Indigo.
Thank you fot the link!
Unfortunately, not being a subsriber of CoDe magazine I couldn't read the
whole article. So I not completely understand what you mean by saying
"Enterprise Services offers better performance than both Remoting or Web
Services" - since former is a platform (pooling+contexts,transaction,loosely
coupled events and so on) and laters are mere transport (of course, a little
bit more than that but...).
> Honestly, this surprised me. However, he was talking specifically about
> .NET machines communicating amongst themselves, and that eliminated the
> normal marshalling overhead you get if you communicate wit non .NET
Communication is not a real point of consideration for me (though if we try
to compare Enterprise Services and Web Services in that context - chanses
are that old DCOM will beat Remoting (or even more likely SOAP) even though
.NET Interop takes place for Server Activated applications)... but, say,
scalability is the point (Dynamic Load Balancing for example). That is why I
asked about real life examples... and still interesting in :-)
Ed.