2. Additions ofbridge.CloudContext:
public int getMethod(String m);
public int getDefaultMethod();
public String getDefaultApplication(int method);
Looking from the Authentication class, i would prefer to have the
following method added overthere:
-public String[]
Eduard Witteveen wrote:
2. Additions ofbridge.CloudContext:
public int getMethod(String m);
public int getDefaultMethod();
public String getDefaultApplication(int method);
Looking from the Authentication class, i would prefer to have the
following method added
Eduard Witteveen wrote:
Hmm, you didnt solve that one with a callback class,.. just curious,
could i have a peek? :D
1.8.0 package with source code can be found on :
http://testsites.omroep.nl/aselect/mmbase-aselect.zip
It depends on method=delegate.
Michiel
--
Michiel Meeuwissen
Well, the proposal was just to not make the difference any
more. So indeed I proposed to make Cloud.getUser() to return
a UserContext, so you could simply feed it to the
check-methods of authorisation implementaiton without any trickery.
We could also try backwards-compatibility with a
Hi,
I think the described changes are a great improvement. The separation
between User and UserContext has presented me with similar problems, but
one is missing, I think.
In some pieces of code I call Authorization.check(UserContext, int,
Operation) myself. This method needs a UserContext
] Request for comments: changes in security
Hi,
I think the described changes are a great improvement. The
separation between User and UserContext has presented me with
similar problems, but one is missing, I think.
In some pieces of code I call Authorization.check(UserContext, int
