Pierre van Rooden wrote: > > cloudContext.getAuthentication().getDefaultMethod();
This would be ok with me too. I was reluctant to do that because Authentication also contains a method like load(MMBaseCop, ResourceWatcher, String), which then all should also be 'part of the bridge', which perhaps goes a bit too far, because before you know it, you need a complete mmbase.jar on the rmmci side... And actually, I think you should not be able to reload security like that... You would suddenly also be able to acquire a User object without a Cloud, which seems a bit un-bridge-like. > Depending on the approach chosen. A little more typework, but I think a > lot better than implementing more (possibly confusing) methods on > CloudContext. My idea was not to avoid typework, but to at least somewhat confine the scope of the bridge. So, I would still opt for wrapping only those few new methods in the bridge. Michiel -- Michiel Meeuwissen mihxil' Mediacentrum 140 H'sum [] () +31 (0)35 6772979 nl_NL eo_XX en_US _______________________________________________ Developers mailing list [email protected] http://lists.mmbase.org/mailman/listinfo/developers
