Web Server Flexibility. Currently we only support the Java Web
Server. In future releases, any web server that can run Java servlets will be able
to host the CQ engine.
Database Support. Currently only MS-SQL server is supported on NT. In
future releases we will support other SQL-92 compliant (and JDBC compliant) databases as
the metadata repository or monitored data source.
Port Restriction. The restriction of ports is not inherent in the
design of JCQ; future releases will allow for more convenient configuration.
Client Software. The client software does not currently support all
administrative CQ functions such as editing and deleting CQ's. Also, the client only
supports restricted SQL statements. These features are available in other versions,
and will be incorporated into a future NT release.
Arbitrary Action. Currently, the most common way of sending
notifications is via email. This is not the only available method; there is also an
external call which can call an arbitrary URL. While this is sufficient for
triggering any action, we plan on extending the notification capabilities by allowing the
execution of arbitrary (system-admin approved and installed) Java code.
CQ Indexing. When a large number of triggers over the same data source
are present, there is a heavy demand placed on both the data source and the CQ
engine. CQ Indexing will help alleviate both the load on the source and the CQ
engine by dynamically combining similar triggers and queries, delivering individualized
service with less overhead.
