 | | |
| \ \ \ \ |
| | Excerpt from: Into the MyST | | | August 31, 2003 | | Perhaps a new term, this appropriately describes a new and emerging set of business and technical requirements. | |
As the use of
Weblogs begin to filter into businesses and enterprises in support of
km-related processes, new requirements will emerge.
The nature of a
Weblog Application Server indicates that there are some
interesting breakaway’s from traditional app servers that will likely create a
new segment. One simple distinction is that application servers
generally don’t prescribe a data model, whereas a Weblog Application Server
should.
Weblog’s (by
definition) imply that a data persistence model comes with the product. Storing
and retrieving blog posts is a basic requirement, but the architecture must
support more than a simple collection of data fields to participate in effective
and broad enterprise use. The MyST object
model represents the persistence store for the MySmartChannels Weblog
Application Server and provides an extremely abstract system for
storing and managing Weblog content.
What makes the
MyST platform suitable for enterprise use [and defining it as an
application server] is its high degree of abstractness.
Weblog products are limited in scope concerning the data types that they
can handle. We believe this is an important distinction if you are holding your
technology to the standards of “platform” or “application server”. The MyST
platform provides mechanisms for dealing with arbitrary data types and XML
document payloads. Although MySmartChannels provides a useful demonstration of
basic Weblog information, the platform is designed to provide much greater
depth so that it may participate in deeper enterprise integrations. | |
| |
|
 |
|
|
