1. Merging of org.mmbase.bridge.User and org.mmbase.security.UserContext.
After some concideration I think that getting rid of org.mmbase.bridge.User is maybe not a big problem.
It does cause some backward incompatibility, but I think the changes are mostly minor.
2. Additions of bridge.CloudContext:
public int getMethod(String m);
public int getDefaultMethod();
public String getDefaultApplication(int method);
If you add UserComtext to bridge, you can also add security.Authentication to bridge. Persoanlyl, I think these methods are confusing, their anmes imply the wrong behavior, and I advocate to use:
public org.mmbase.security.Authentication getAuthentication();
or, perhaps:
public org.mmbase.security.MMBaseCop getMMBaseCop();
The latter gives more info, thoiugh you generally don't need most of that. You can the obtain the default method with:
cloudContext.getAuthentication().getDefaultMethod();
or
cloudContext.getMMBaseCop().getAuthentication().getDefaultMethod();
Depending on the approach chosen. A little more typework, but I think a lot better than implementing more (possibly confusing) methods on CloudContext.
-- Pierre van Rooden Mediapark, C 107 tel. +31 (0)35 6772815 "Anything worth doing is worth overdoing." _______________________________________________ Developers mailing list [email protected] http://lists.mmbase.org/mailman/listinfo/developers
