We all know and love Don, but we know how religious he can be sometimes. Especially when what he tells the audience coincides with the current 'party line' of Microsoft :)
If you need proof, just remember that giant flop "Build all your multi-tier web applications with COM+ transactional components." This was the official Microsoft strategy a couple of years ago. I personally managed to screw quite a few $$$ by making wrong architectural decisions back then. Looking back, writing middle-tier COM+ components with VC++/ATL (or even VB) was wrong every time in terms of performance and maintainability, as compared to plain old ASP script. What happened a year after that? Well, even though it was half-mouthed, every Microsoft and non-Microsoft employed expert who knew their stuff suggested that you avoid transactional components at all costs for read-only operations, and use them in read/write scenarios only after giving a long a hard look at the real needs of your application. (The same applies to Enterprise Services nowadays, BTW) XML is great, guys. I really love it. However, before you plunge into the "XML everywhere" abyss, remember that there are passengers for every train (as we say here in my home country :) -- binary data representation is here to stay for quite a few purposes and applications. XML is a panacea when you need to communicate between different apps. But intra-application communication, when you control both ends of the channel? Think twice... </rant> Just to let everybody know, I am not a Microsoft basher. In fact, until two years ago, I was an MSDN Regional Director (not a MS employee, but a honorary unpaid partner position). I love .NET -- it was long overdue, and put Java back where it belongs -- in the "we won't do it on Microsoft software, even if it's slower and buggier" camp. To reiterate, XML is great, but not as great as to make the "there is no such thing as a silver bullet" axiom untrue. Maybe Ingo could pitch in here with some strategic thoughts on Remoting. He is, after all, the foremost (publicly known) non-Microsoft employed expert on the subject. -----Original Message----- From: Moderated discussion of advanced .NET topics. [mailto:[EMAIL PROTECTED] On Behalf Of Philip Nelson Sent: 17 Ноември 2003 г. 19:09 To: [EMAIL PROTECTED] Subject: Re: [ADVANCED-DOTNET] How to comunicate from .NET with an older C++ library? > I can think of one more approach that will give you better performance > (although it still won't be nearly as fast as the shared memory > solution): .NET remoting. I'm sure others here can elaborate much better than I, but .net remotings seems to be heavily de-emphsized in Whidbey. Don Box was openly derisive of remoting and of the idea of strong typing across processes. Indigo will also have the ability to do a binary format of xml to dramtically reduce the overhead as I understood the presentation at the PDC. So, depending on your timing, you may want to consider how Whidbey might influence your decision. =================================== This list is hosted by DevelopMentorR http://www.develop.com Some .NET courses you may be interested in: Guerrilla ASP.NET, 10 Nov 2003 in London and 26 Jan 2004, in Los Angeles http://www.develop.com/courses/gaspdotnet Guerrilla .NET, 8 Dec 2003, in Los Angeles http://www.develop.com/courses/gdotnet View archives and manage your subscription(s) at http://discuss.develop.com =================================== This list is hosted by DevelopMentor╝ http://www.develop.com Some .NET courses you may be interested in: Guerrilla ASP.NET, 10 Nov 2003 in London and 26 Jan 2004, in Los Angeles http://www.develop.com/courses/gaspdotnet Guerrilla .NET, 8 Dec 2003, in Los Angeles http://www.develop.com/courses/gdotnet View archives and manage your subscription(s) at http://discuss.develop.com
