a) COM+ is not going to die unless Windows dies. b) Indigo performance is nothing you should look at when the product is not even Beta.
c) (to the original poster) Use ASMX by default and ES if you need the services. Forget about Remoting's existence for the network edge unless all you ever want is a reasonably smart data formatter for raw TCP sockets. -cv -----Original Message----- From: Unmoderated discussion of advanced .NET topics. [mailto:[EMAIL PROTECTED] On Behalf Of ADVO Sent: Friday, June 25, 2004 2:21 PM To: [EMAIL PROTECTED] Subject: Re: [ADVANCED-DOTNET] Middle-Tier Hosting: Remoting vs. Enterprise Services Actually, Indigo is the only communication/transaction-level platform that Microsoft will support. COM+ (with Enterprise Services as well) will eventually die because Indigo will provide what COM+ can do and more. Indigo will add transparency to you application regarding location, communication way to connect to your remote object/service. The object may be just local, and will be efficiently called inside your process if you wish. It will provide transaction service using which you may execute not only distributed transaction through internet, but also long-running transactions (with ability to roll-back performed operations if the transaction is aborted). BUT.... 1. This is what Microsoft promises. 2. I wouldn't expect we will get the really reliable solution by 2005. Microsoft planned to release beta version of Indigo in 2004. 3. And I'm now sure about performance: My colleague participated Microsoft's seminars regarding Indigo. Guys there presented simple communication between two distributed web services. The message communicated through Indigo was smth. like "Hello world", but he was disappointed with the performance - it took about 10 sec (!) per message. Of course Microsoft will improve that but I still worry about what we will have to work with. Good luck, Roman Koreshkov -----Original Message----- From: Unmoderated discussion of advanced .NET topics. [mailto:[EMAIL PROTECTED] On Behalf Of Andy Smith Sent: Thursday, June 24, 2004 8:59 PM To: [EMAIL PROTECTED] Subject: [ADVANCED-DOTNET] Middle-Tier Hosting: Remoting vs. Enterprise Services I'm getting conflicting opinions on what is the best technology to host middle-tier .NET components. Mine is a typical 3-tier scenario, with each of the tiers on separate boxes. I've got both internal and external clients that will use these services (components). I was working in an IIS hosted/HTTP binary remoting direction, but now it's been suggested to me that not only will Enterprise Services give me far greater productivity (because of the ability to leverage it's services - transactions, security, etc), but also that it's actually the best migration path to Inidigo, contrary to what many say (including Don Box). Also I'm told that Enterprise Services do NOT involve interop "most of the time". I'm just looking for any educated opinions that anyone may have on this topic. I've read mostly negatives about ES and .NET, and never heard that it's the best migration to Indigo. I've got several projects coming down the pipe and I've got to make some decisions quickly, so any input is greatly appreciated. Thanks! =================================== This list is hosted by DevelopMentorR http://www.develop.com Some .NET courses you may be interested in: NEW! Guerrilla ASP.NET, 17 May 2004, in Los Angeles http://www.develop.com/courses/gaspdotnetls View archives and manage your subscription(s) at http://discuss.develop.com =================================== This list is hosted by DevelopMentor(r) http://www.develop.com Some .NET courses you may be interested in: NEW! Guerrilla ASP.NET, 17 May 2004, in Los Angeles http://www.develop.com/courses/gaspdotnetls 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: NEW! Guerrilla ASP.NET, 17 May 2004, in Los Angeles http://www.develop.com/courses/gaspdotnetls View archives and manage your subscription(s) at http://discuss.develop.com
