Nico Klasens wrote:
> Class-security is the advanced way to get a cloud, but there are many
> situations where you don't want to configure a lot. You just want a
> cloud to create some nodes.
You don't have to configure a lot. You simply specify a class, and which
user it must receive if it requests a cloud by 'class'.
> The docueentation on the site is not in sync yet with the current
> implementation. Version 1.2 has the possibility to get a cloud based on
> a name.
Yes, the documentation of class-security is not very complete
either... That's why I take the opportuninty to advertize it a bit like
this :-)
> You can do for example.
> CloudProviderFactory.getCloudProvider().getCloud(), but also
> CloudProviderFactory.getCloudProvider("mycloud").getCloud()
A simple cloud can simply be gotten with
ContextProvider.getDefaultCloudContext().getCloud("mmbase");
and a logged in cloud can be gotten with
ContextProvider.getDefaultCloudContext().getCloud("mmbase", "class", null);
Which strikes me as hardly more cumbersome..
(this 'mmbase' argument is irritating me, but well...)
> 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).
Michiel
--
Michiel Meeuwissen mihxil'
Peperbus 111 MediaPark H'sum [] ()
+31 (0)35 6772979 nl_NL eo_XX en_US
_______________________________________________
Developers mailing list
[email protected]
http://lists.mmbase.org/mailman/listinfo/developers
