Looked at the 3.1a1 distribution, and starting to get my head around
it. Some nice features and concepts ... good work!
Not sure how some of the areas we need for our environment fit
into the current structure or future plans e.g.
* Dynamic applications/components - the concept of "long running"
VM sessions into which we dynamically load and unload
components and applications. At startup all we have is an "empty
shell" and the ability to request loads. Classes would get unloaded
when dead to prevent memory hogging over time.
* Dynamic remote machine deployment - the concept of a pool of
host machines with minimal software installed (e.g. the JAVA VM
and a Bootstrap Loader). Ideally we'd remotely deploy initially the
Execution Environment (e.g. Avalon/Phoenix) and then once
running specific components and applications.
* Cross VM pooling - allow applications/components to be
distributed across VM's and machines, with ways for them to be
accessed and use in a "single image" manner e.g. via directory
services, proxies etc.
* Application and Component caching - to allow a component to be
rebuilt and redeployed, without knocking out running versions until a
control/sync point is determined.
* Multiple application/component instances - a single component or
application being loaded once, but having instances to meet
demand (either for reasons of volume or partitioning).
* Locally silent operation - minimal logging to the local file system
(apart from crisis, panic or debug logs). Other logging being via a
flexible "log connector" approach so that log output can be gathered
centrally/remotely.
Feel free to ignore or disregard if these are seen as outside the
scope of Avalon and Phoenix.
-- Rob --
SoftSell Business Systems, Ltd.
' testing solutions for a changing world '
+44 (20) 7488 3470
www.softsell.com
[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
