Leo Sutic wrote:
DE-AVALONIZATION
I did put AltRMI into the UTILITIES layer, even though it has
dependencies on Phoenix. What I was thinking about was a split
into Avalon and non-Avalon code. That is, AltRMI should be a
replacement for RMI in every aspect, but still be deployable
as a block in Phoenix (the Publisher, for example).
To me, this is the problem. AltRMI is IMO a low level library.
It is mixing in what should be a Cornerstone component with
the core AltRMI library. If those two parts were separated,
we loose the circular dependency....
From my recollection, Paul and the other AltRMI developers are
working on making it completely separate and without external
dependecies.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
