ASP.NET architecture changes
Explains how ASP.NET architecture changed since the 5.3 release.
Both the SDL Tridion 2009 and the SDL Tridion 2011 releases resulted in changes to the ASP.NET API for Content Delivery.
In SDL Tridion 2009, the architecture of Content Delivery was changed. The following image shows the Content Delivery architecture in SDL Tridion 5.3:
The following image shows the Content Delivery architecture introduced in SDL Tridion 2011:
The architecture introduced in 2009 implemented some important changes:
- The Java Virtual Machine (JVM) no longer runs in a Windows service, but is hosted in the same IIS worker process as ASP.NET
- The architecture fully supports multi-threading.
- The architecture no longer relies on inter-process communication.
- If you are running an ASP.NET Web site, the following separate Windows services are no longer needed:
- Content Broker WAI
- Content Delivery Broker
- Content Broker Linking
- ASP support is deprecated—in R5, ASP used the COM API directly from code.