On Thu, Nov 21, 2002 at 11:28:12PM -0800, Stefano Mazzocchi wrote:
> >1) Micro Container--a Tweety like container that can operate in J2ME. It..
> >2) Standard Container--the result of merging Merlin and Fortress. It..
> >3) Server Container--Phoenix. It identifies the requirements for a root..
+1, this is what Nicola also proposed a while back.
> You would see me happy on this only if each container used the
> underlying one.
>
> That is: Merlin's Fortress is based on Tweety and Phoenix is based on
> Merlin's Fortress (can we come up with a better name for this, please?)
>
> That would solve all my concerns and would force people to work together
> and create a community because they would share not only the syntax and
> the semantics but also the behavior. And would force all containers to
> keep in synch.
One possible approach at achieving more reuse could be something
what PeterD and I spoke about a few weeks back archived at:
http://marc.theaimsgroup.com/?l=avalon-dev&m=103719498600580&w=2
or some variation of it.
Essentially the idea was to create a common underlying 'container'
model that could be reused inside container implementations.
The thread was more directed at providing backwards compatibility,
but could be applied to increase reuse - albeit more using a
composition approach rather than inheritance.
PeterD had some good comments in the thread though, I still have to
get back to him about them. Anyway, just thought I'd bring it up.
On the topic of having a single container, I'm all for it - I think
what Berin/Stefano describe above could actually be considered a single
container, just layered upon each other to extend the container's
target scope (ie. small -> mid/embedded -> large/server scale).
Just my 2c AUS :)
Cheers,
Marcus
--
.....
,,$$$$$$$$$, Marcus Crafter
;$' '$$$$: Computer Systems Engineer
$: $$$$: ManageSoft GmbH
$ o_)$$$: 82-84 Mainzer Landstrasse
;$, _/\ &&:' 60327 Frankfurt Germany
' /( &&&
\_&&&&'
&&&&.
&&&&&&&:
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
