> >> So the actual "doing" part is done in user land and it is only the glue > >> that exists in the kernel. When no .sar is loaded to provide > service then > >> default implementations of Facilities are used. > > > >Hmm. An MBean is allowed to get a reference to the MBeanServer by > >implementing > >some specific interface. It might make more sense to just > request a Facility > >from the MBeanServer; this allows for more generic MBeans. This needs a > >little > >more thinking, I think. Actually, when we keep the "lightweight" idea in mind, none of the jmx stuff should be needed so this is not a good idea. But, if phoenix should run on a really tight memory space, it might make sense to not even have the default implementations directly and put them all in special "facility .sars". > >> I was hoping that the impact of JMX on the system would be > >> minimal - how do > >> you see it? I assume there will need to be entries in config files that > >> mark particular apps/blocks as manageable but is there a need to pu JMX > >> specific information in the config file ? > > > >I'm not entirely sure yet. If we really use DynamicMBeans for everything, > >no. If we also use standard MBeans, or want to provide the option, it is > >definately the most logical thing to do. But I'm not sure whether it is > >really neccessary... > > sounds good. > > >> Would it be possible for the services not to extend DynamicMBean but > >> instead a wrapper be used ? > > > >Sure thing. But why? > > The less dependencies the better. One of my long-term goals is to get > Phoenix running on consoles like Playstation2 - thats a while off yet ;) > But I would prefer to keep everything as lightweight as possible - and if > it doesn't *need* to be a dependency then ... ;) got it. JMX should be a plug-in module loaded from a .sar or some related mechanism so it can easily be removed from the system. The one class to change then would be Main.class (or the to-be-created Embeddor, perhaps), which needs to toggle loading of JMX through some command-line option. I was thinking perhaps switching to jmx for loading of Facilities etc, but this is definately not leightweight (as that implies a jmx adapter and other 'heavy' stuff). We're going for added complexity to add functionality once more =) thought: perhaps it is not a good idea to have one kernel do everything. Maybe there should be an enterprise-oriented phoenix, a user-oriented phoenix, and a leightweight phoenix (like they've done for the java platform. Well? greetz, LSD --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
