RE: Ektron's .NET/ActiveX Solution

MessageThanks for the clarification Tony.

So for the record, please note that the paragraph Tony quoted was from my
description of *CMS300*.  CMS400.NET does *not* use Classic ASP as the
scripting interface for any content contribution functionality nor for the
user interface.  CMS400.NET uses ASP.NET exclusively as the scripting
interface and for the user interface.

I apologize for sticking to this point so doggedly but I want to be sure
that there's no confusion between Ektron's .NET and non-.NET products.

Tim Denby
Ektron, Inc.

  -----Original Message-----
  From: Tony Byrne - CMS Watch [mailto:tbyrne-xROWbLetBU9Wk0Htik3J/[email protected]]
  Sent: Thursday, March 03, 2005 5:50 PM
  To: 'Tim Denby'; [email protected]
  Subject: RE: [CMS] Ektron's .NET/ActiveX Solution


   > The language we chose to build the 100% browser-based user interface is
Classic ASP (this is why Classic ASP is a technical
   > requirement of the system as posted clearly and unambiguously on our
web site - perhaps that's what CMSWatch is saying?).

  Yes, that is what The CMS Report says.  JPW's earlier summary of the
report erred on the vague side.

  To quote from the report:

  "..Note that this is a bundled management and delivery environment. While
CMS300 ships with support for PHP and ColdFusion in the delivery
environment, CMS400 only uses ASPX and both products use ASP as the
scripting interface for all content contribution functionality. In short
..."
  --------------------------------------------
  Tony Byrne
  Founder, CMS Watch
  Silver Spring, MD  USA
  V: +1 301 585 7004
  The CMS Report: http://www.cmswatch.com/TheCMSReport/
  Enterprise Search Report: http://www.cmswatch.com/EntSearch/
  Headline Feed: http://www.cmswatch.com/RSS/cmswatch.xml