> As we pull together the threads of our next project I am slightly
> dismayed to learn of the disputes at the top of Arsdigita as we were
> planning to use the ACS system as a springboard to which we would add
> our subscription based application.
Why should that matter? ArsDigita doesn't control AOLserver, and if
you're planning to use ACS Tcl, then there are several sources of support
available for it besides ArsDigita.
> My main concern is the porting of the ACS system to Java. To me this
> looks rather like a fashion statement and is something I would seek to
> avoid because it will surely just add another tent to the circus.
To have credibility with Fortune 500 companies, it helps a lot to be
Java-based rather than Tcl-based. It's that simple.
> Is the future direction of AOLServer likely to incorporate integrated
> Java (and move away from TCL)?
No. Tcl will be the primary extension language of AOLserver for the
foreseeable future. (I'm sure Jim Davidson will correct me if I'm
wrong).
>
> Can we safely base our software infrastructure strategy on AOLServer
> + TCL (with or without ACS) or does the ARSDigita move towards java
> presage a similar shift in AOLServer?
You can safely use AOLserver + Tcl, with or without ACS.
