This content has been marked as final. Show 4 replies
There are customers who have deployed Endeca with ASP.NET and the choice between RAD and the lower-level APIs depends on how much the RAD interface supports your UI needs. In our most recent release (Endeca Commerce v3.1), we no longer provide the RAD Toolkit as we support an HTTP interface with our Assembler framework. Many of our .NET customers, especially those on v4, prefer to consume the XML responses we provide with the Assembler. We still provide the lower-level Endeca.Navigation dll in Platform Services v6.1.3, which is shipped as part of the Endeca Commerce v3.1 release.
What is the recommended direction taking into account the future product life cycle? We're upgrading from 6.0.2 with RAD.NET. Will the Presentation API continue to be supported or going forward should we consider refactoring our code to use the Assembler Framework? Are there performance considerations?