Re: [Fwd: Re: [PEAR-DEV] User authorisation class]

> > Storing the user object in a session and only connecting to the data > container on login is already implemented, so this is not a problem. > The ACL can also be refreshed during a session by calling a > readRights() method which reconnects to the container and retrieves the > latest ACL information. > > I guess I´ll go for a combination of solutions 1 and 3: A new > connection object will be created for each listet server. That object > can also be a SOAP object and will be in most cases. > The SOAP server that is connected can in turn be configured to query a > list of storage containers. Sounds good to me. Keep in touch, please. > > The reason why I choose SOAP over XMLRPC? 1. Currently it´s a buzzword > that makes managers go "aaah" and 2. I have more experience with that > than with XMLRPC :-) Well that is reason we have so many meaningless strings of letters, anyway. Managers aways goes "aaah" (meaning: Duh!?) when we do that :) And we love that, doesnt we? To me sounds fine, but XMLRPC looks simple to me, since a dont have experience with SOAP :) S.Rocha