>> What about my (2) ? How can i set something like 'permissions' for every
>> method so that method_call event will have access to them when method is
>> called ? I was using a decorator for all of this, for example:
>> @login_log_decor( send_mail=True, has_domain=True, perms={"and": ["aaa",
>> "bbb"], "or": []} )
>> def myfunc(....):
>>
>
>I thought about this. i think the best way to do this is to add a new
>argument to the rpc decorator like this:
>
>@rpc( (...), _udp=SomeObject(send_mail=True, has_domain=True,
>perms={"and": ["aaa", "bbb"], "or": []} )
>
>which will be accessible from ctx.descriptor.udp from both events and
>methods. this is committed in my fork. does that help you?
i think this will do the trick, thnx
>another thing, could you please fork rpclib and commit your php tests?
>just something like the ruby tests, nothing fancy.
where can i find that ruby tests ?
azur
_______________________________________________
Soap mailing list
[email protected]
http://mail.python.org/mailman/listinfo/soap
