Andreas Frei wrote:
Hi
I was looking around in the avalons community for a small footprint kernel. As fare as I understand Merlin targets a server infrastructure where resources and CPU power is not THE limiting factor. Maybe I am also wrong, but when I look through the dependencies I see quite heavy-wight components (xml-stuff, excalibur?)? Are there any results of runtime memory consumption for a basic, lets say "hello world" component?
I'm currently developing a homebrewed kernel which actually is in some
parts similar to the avalon-framework, well not that nice and thought
through. I just stepped over this avalon stuff and was surprised to find
some ideas again in the framework and merlin. As I don't want to develop things which are already done I wonder if
merlin could be/is a kernel for small devices where I target J2ME(CDC)
devices like an iPAQ? My homebrewed kernel works currently on such
devices (well still with jre1.3) but my goal is to move it to j2me.
As merlin is already that enhanced, my question is if it is of interest to have such a kernel for small devices? I looked at picocontainer and nanocontainer but in small devices I would still need some meta information about the components as this components are part of deployment and should be advertisable to other small devices. To find such components in its environment the meta information would be advertised like in a P2P (JXTA/JXME) infrastructure.
What are your ideas about such a small footprint container or do you have some other links?
The recent work on the seperation of the repository facility from the internals of merlin opens up a bunch of possibilities for scaling down merlin. For example - the current merlin runtime needs a bunch of stuff to handle things like XML configurations are so forth - however - much of this could be parameterized - so for example one could declare a facility to handle configuration, maybe another facility for logging, and another for assumbly. Merlin could then bring these in dynamically. In such a scenario the core merlin system would be rather small - but we are not there yet. There is still a lot to do in both kernel facility management and plugable lifecycle stage handlers.
If I was doing this from scratch - I would start with avalon-repository, avalon-util, avalon-meta as the basic platform and maybe leverage avalon-composition but focussed on serialized descriptors (i.e. no runtime xml).
Cheers, Steve.
Regards, Andreas
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--
Stephen J. McConnell mailto:[EMAIL PROTECTED]
|------------------------------------------------| | Magic by Merlin | | Production by Avalon | | | | http://avalon.apache.org/merlin | | http://dpml.net/ | |------------------------------------------------|
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
