1. How many cfm and jsp files are there combined...are those part of the
html files? If they are... does the metrics progam count just the
templates... what are the parameters?
Oh, that was just the static HTML pages. macromedia.com is a large static site with CF applications on it rather than a dynamic site.
There's about 2,000 CF files (.cfm and .cfc) on the main Dylan system plus the remaining legacy code on the former-Allaire cluster (Partners app amongst others). There are no JSP files. There's about 1,200 Java source files (some classes are used from CF, some are standalone back end applications). That's based on the most recent CVS drop to my machine. There may well be a few more pages by now - I haven't needed to work on the website for a while so my CVS tree may be a bit out of date.
2. How many of these are "external" intranet vs internet applications.
All of that is on www.macromedia.com - although the CF code does include the data admin programs for the customer-facing applications (so they are effectively internal).
3. I can conceed that "breeze" may be done on a different platform... don't
know.
I am only a user of Breeze Live - I'm not familiar with the construction of the application itself.
You mention cgis as 59, but you don't give statistics for .cfm, or .jsp.
See above. I gave numbers for the web server (which is static content that we manage manually using Dreamweaver - hence we automatically count files every night). CGIs live on the web server. The files on the app servers are managed using CVS which I've given figures for above. Nearly all of the CGI applications pre-date Macromedia's acquisition of Allaire so Perl was often used for small applications (and the various mod_perl plugins used by our Apache setup, e.g., Flash detection and /go/ URL mapping).
Around the time Macromedia acquired Allaire, we were already planning to rewrite the BroadVision applications and our intended direction was to use JSP. Of course, once we had ColdFusion available to us, we choose that instead and over the last couple of years we've rewritten all the original BroadVision applications (trial downloads, product registration, membership, developers' exchange, online store, member-only-downloads and a few smaller apps) as well as migrating legacy CF apps from the former-Allaire systems and introducing a number of new applications... I think our QA team tests around 30 applications each time we make a release (and we make a release every two weeks now - we used to make a release every week for the first six months or so after the initial Dylan launch).
5. Lastly... I am also familiar with "auto-generation" of pages and templates.
See above - we do not auto-generate HTML pages.
#. Livedocs are interesting, but that is a side topic to the original concept. They would be in HTML regardless.
The LiveDocs system is written in Java and CF - the documentation itself is HTML.
Regards, Sean
----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email
to [EMAIL PROTECTED] with the words 'unsubscribe cfcdev' in the message of the email.
CFCDev is run by CFCZone (www.cfczone.org) and supported by Mindtool, Corporation (www.mindtool.com).
An archive of the CFCDev list is available at www.mail-archive.com/[EMAIL PROTECTED]
