ATL Server vs ASP.NET
-
To me it seems as if MS is not trying very hard to push ATL Server as a means of developing web apps. What do you guys think? Could it be that ATL server has too few advantages over ASP.NET? After going through one of their tutorials (a very very good one by the way) I couldn't help but think that ATL Server is at least an order of magnitude more complicated than going the ASP.NET route. And I haven't managed to find any good reasons why someone should rather use ATL Server. Can anyone come up with some good enough reasons? And when God, who created the entire universe with all of its glories, decides to deliver a message to humanity, He WILL NOT use, as His messenger, a person on cable TV with a bad hairstyle.
-
To me it seems as if MS is not trying very hard to push ATL Server as a means of developing web apps. What do you guys think? Could it be that ATL server has too few advantages over ASP.NET? After going through one of their tutorials (a very very good one by the way) I couldn't help but think that ATL Server is at least an order of magnitude more complicated than going the ASP.NET route. And I haven't managed to find any good reasons why someone should rather use ATL Server. Can anyone come up with some good enough reasons? And when God, who created the entire universe with all of its glories, decides to deliver a message to humanity, He WILL NOT use, as His messenger, a person on cable TV with a bad hairstyle.
I'll tell you some reasons: 1. ATL Server will result in fully compiled DLLs. 2. You have no dependencies of the .NET framework. 3. It is the fastest way possible (also ISAPI, native code, no JIT on first request or interpreted language like old ASP, PHP etc.) 4. The Dll is loaded by intetinfo directly. It's not like ASP.NET when a different process asp_wp.exe is loaded that executes your dll. So if you want to build really fast/real time application consider ISAPI and ATL Web Server. As an example, the E-bay bidding online web site is built using ISAPI. Best regards, Alexandru Savescu
-
To me it seems as if MS is not trying very hard to push ATL Server as a means of developing web apps. What do you guys think? Could it be that ATL server has too few advantages over ASP.NET? After going through one of their tutorials (a very very good one by the way) I couldn't help but think that ATL Server is at least an order of magnitude more complicated than going the ASP.NET route. And I haven't managed to find any good reasons why someone should rather use ATL Server. Can anyone come up with some good enough reasons? And when God, who created the entire universe with all of its glories, decides to deliver a message to humanity, He WILL NOT use, as His messenger, a person on cable TV with a bad hairstyle.
Passport.com uses ATL Server regards Kannan
-
I'll tell you some reasons: 1. ATL Server will result in fully compiled DLLs. 2. You have no dependencies of the .NET framework. 3. It is the fastest way possible (also ISAPI, native code, no JIT on first request or interpreted language like old ASP, PHP etc.) 4. The Dll is loaded by intetinfo directly. It's not like ASP.NET when a different process asp_wp.exe is loaded that executes your dll. So if you want to build really fast/real time application consider ISAPI and ATL Web Server. As an example, the E-bay bidding online web site is built using ISAPI. Best regards, Alexandru Savescu
Ok, so in a nutshell, the only advantage is raw speed. Almost sounds like we're back to the old C++ vs Java debate :-) And when God, who created the entire universe with all of its glories, decides to deliver a message to humanity, He WILL NOT use, as His messenger, a person on cable TV with a bad hairstyle.
-
I'll tell you some reasons: 1. ATL Server will result in fully compiled DLLs. 2. You have no dependencies of the .NET framework. 3. It is the fastest way possible (also ISAPI, native code, no JIT on first request or interpreted language like old ASP, PHP etc.) 4. The Dll is loaded by intetinfo directly. It's not like ASP.NET when a different process asp_wp.exe is loaded that executes your dll. So if you want to build really fast/real time application consider ISAPI and ATL Web Server. As an example, the E-bay bidding online web site is built using ISAPI. Best regards, Alexandru Savescu
I compared the way to build web services with ASP.NET and ATL Server. I would say that it is a little more work and more complicated to use ATL Server. But for sure there is place where it is certainly needed. Laurent Kempé Tech Head --- Old programmers never die, they just branch to a new address.
-
I'll tell you some reasons: 1. ATL Server will result in fully compiled DLLs. 2. You have no dependencies of the .NET framework. 3. It is the fastest way possible (also ISAPI, native code, no JIT on first request or interpreted language like old ASP, PHP etc.) 4. The Dll is loaded by intetinfo directly. It's not like ASP.NET when a different process asp_wp.exe is loaded that executes your dll. So if you want to build really fast/real time application consider ISAPI and ATL Web Server. As an example, the E-bay bidding online web site is built using ISAPI. Best regards, Alexandru Savescu
****Alexpro wrote: 1. ATL Server will result in fully compiled DLLs. So does ASP.NET - it compiles the pages. ASP.NET compilation in the end is more efficient than ATL Server compilation. Use ATL server only when you are expecting lot of interop. I think ASP.NET is still the fastest way to develop. Step back, rub your eyes, take a deep breath, stretch a bit, and reflect on the relative importance of CP, CG, the age / travel time sustained by supposedly 'fresh' cheese curds, and Life in General. - Shog9
-
To me it seems as if MS is not trying very hard to push ATL Server as a means of developing web apps. What do you guys think? Could it be that ATL server has too few advantages over ASP.NET? After going through one of their tutorials (a very very good one by the way) I couldn't help but think that ATL Server is at least an order of magnitude more complicated than going the ASP.NET route. And I haven't managed to find any good reasons why someone should rather use ATL Server. Can anyone come up with some good enough reasons? And when God, who created the entire universe with all of its glories, decides to deliver a message to humanity, He WILL NOT use, as His messenger, a person on cable TV with a bad hairstyle.
Like I said yesterday, for web applications, ASP.NET is a better choice. But for web services, especially if you already have some C++ code written, ATL Server is a way to go. I vote pro drink :beer: