David, > Hard to know. We do have the minimal jboss configuration, which is a good > starting place: as I recall basically all it can do is deploy .sars. AFAIK
I'm thinking of a minimal that is perhaps smaller than that. I think that the MBean API + proxies should be sufficient for many clients. > It's a lot easier for me to think about the container starting first, and I > think it will provide less surprising performance, but I'm not sure we can Isn't Dain's method just lazy instantiation (by definition harder to measure performance-wise)? I imagine a client proxy factory that 1) checks for an mbean server, creates it if necessary, and then 2) checks if required client-side MBeans are loaded and then loads them if necessary, before returning the proxy. Either way, this all sounds good. Too bad I don't have a real use for it yet ;) - Matt ------------------------------------------------------- This sf.net email is sponsored by: See the NEW Palm Tungsten T handheld. Power & Color in a compact size! http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
