Margaret/Ray/MM, thanks for the insight into the future of Spectra, and like
others I have a few questions and insights....
>>The COAPI is one part of Spectra -- the
>>other services, the Webtop, etc. making up the rest. We see the COAPI as a
>>set of tags and services for managing content. It's this technology that
>>we're re-architecting now in Java for inclusion in a future version of the
>>ColdFusion server.
Okay, and correct me if I am wrong, the COAPI *IS* effecitively Spectra?
++ extracts from Allaire Spectra Docs
*** At Allaire Spectra's core, technically, is a programming model dubbed
the ContentObject API, or COAPI
"** The ContentObject API, or COAPI, forms the foundation for all Web
systems built and managed with Allaire Spectra. Using an object-based
programming approach, the COAPI is used to model the information assets and
business processes specific to your organization.**
**All key services provided by Allaire Spectra leverage the COAPI, and
therefore all applications and sites built on the COAPI can easily leverage
these additional services**
Spectra is simply a model based around this technology described above. The
six core services are delivered and managed through the COAPI.
Indeed other roles and services have a crucial part within it as it stands
but the Webtop is simply an app built with the Spectra method (and as was
always stated, the Webtop is more of a shortcut to repetitive tasks
etc...and was meant as help app for the newbie?)
So in this mould - if the entire COAPI is built into CF.X then surely there
is NO NEED FOR THE CSS or SPECTRA as a whole?
Surely you can't be serious about customers still buying Spectra either in
the future or at present when it will be bundled with with the server
technology (users are not that dumb are they?), which will in my opinion
would have to dramatically increase in cost to recupe lost revenue for
Spectra sales and the technology being adopted..
Effectively CF.X is going to be a hybrid product of ColdFusion, JRun, and
Spectra[?] with maybe a new development platform say the COAPI Studio which
will allow developers to utilise and integrate all these services into
scalable applications.
With the present outlook for Spectra - you would be running two "versions"
of exactly the same product - one open source and one java based within the
server technology. If one changes, say a tag within the CSS model, it would
have to change within the server technology which would lead to endless
service packs and/or patches which would lead to massive costs.?!
This leads me to a subject which I think has been overlooked and also, I
think, is Spectra howitzer - the ContentObject Database! Jeez, whats going
to happen to that? this would have to ship with the server tech too? Or will
this only be available to Spectra license holders? without the CODB and
CO's, the COAPI is effectively useless, as it is this excellent DB schema
(for me anyway) which attracts developers - a DB which you do not need to
rebuild for a new app/job? its a RDBMS dream.....
I think that the users of both technologies could do with more information
regading where their $ will be going, I personally would like to see
Spectra and all its core services adopted and rolled into CF.X (I would
happily pay a little more for the server tech with these services on board.)
But hey thats my �0.02p but I hope others can add.
Neil
<!------------------------------
Neil Clark
Senior Web Applications Engineer
Spectra / CF / XML / Cerebro
Macromedia Alliance Partner
MCB Digital Limited - London
[T]: 020 8941 3232
[F]: 020 8941 4333
[M]: 07719 448 227
[E]: [EMAIL PROTECTED]
-------------------------------->
'A goal is not always meant to be reached, it often serves simply as
something to aim at.'
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
------------------------------------------------------------------------------
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/spectra_talk or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
