Stephen McConnell wrote:
Berin Loritsch wrote:
Doug Lea's Concurrency Utils
Need to get the manifest into something rationale before a release.
Huh? Translate, please.
Excalibur Event
More info needed from you - I'm feeling nervouse folowing recent changes
and comments.
Info only comes to those who ask questions.
Excalibur Container (i.e. the lifecycle extensions)
Need to migrate to Sandbox Lifecycle.
?? Why ??.
Look, we can easily incorporate the classes in Excalibur Container into
Fortress for the time being, and blow away the Excalibur Container
project. Or, even better we can merge Fortress overtop and call it
Excalibur Container (Codename: Fortress).
Either way, the interfaces are still present for a Merlin release.
If Sandbox Lifecycle has the same exact interfaces (i.e. the package
and interface are the same), then you can use that in Merlin and
Fortress can include them for the release.
No released product should depend on an unreleased or alpha project.
All Sandbox code is unreleased, alpha, or beta.
Excalibur Instrument**
-1
Problem until instrument provides plugable transpost or a RMI solution
is in place.
Transport is pluggable. In fact no transport is even necessary.
Excalibur AltRMI
This is linked to Instrumentation if I understand correctly. It is also
in under discussion as a incubator candidate. I don;t want tto get into
a AltRMI depedency becauase of an Instrumentation dependenty. I think
we need to sort the Instrumentation depedency first.
AltRMI is *optional*. If the user doesn't want it, they do not need it.
Does that aleviate fears?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
