Michiel Meeuwissen wrote: > > Which strikes me as hardly more cumbersome.. > > (this 'mmbase' argument is irritating me, but well...) >
This 'mmbase' is configurable in the 1.2 CloudPrivoider > >> The cloudprovider is just a simple utility around the different login >> methods to mmbase. > > I understand, but still I think that it is a bit silly that that would > be needed in the first place, and that's a reason why I deviced 'class' > security. Sadly not fully fledge available for 1.7, though it can be > compiled for 1.7 (but the security implementation are not adapted so you > still need to provide passwords in classsecurity.xml then). > In many cases you have existing security in an MMBase application that you need to use, the CloudProvider gives you access to these by just configuring. Many times you have a generic component that needs admin access (or even rmi access) and in those cases you dont want to recompile this component to change a context name or the implemented security for it to run in your MMBase application, CloudProvider helps out in many of these every day problems. Also switching (while developing) between rmi access and direct cloud access by simply configuring is an advantage. Wouter _______________________________________________ Developers mailing list [email protected] http://lists.mmbase.org/mailman/listinfo/developers
