This forum has been archived. Please start a new discussion on GitHub.
User access control with glacier2
Glacier2 provides some powerful functions such as the verifier and sessions to deal with the issue of user access control. I searched the forums and found many threads about this topic . The "facade" pattern was mentioned serveral times. Howerver, there isn't a comprehensive stuff on it. Hope one of the future connections may give more through clarify about user access control.
This is a good topic for a future article. However, in the meantime:
This pattern originally came from the GOF book http://www.amazon.com/exec/obidos/tg/detail/-/0201633612/qid=1121431181/sr=8-1/ref=pd_bbs_1/104-9316850-7935934?v=glance&s=books&n=507846.
You can also look here http://www.dofactory.com/Patterns/Patterns.aspx for some details. Basically the idea is that you present a single (or series of) simplified class in the session, or accesssible from the session that respresent a simplified respresentation of the entire system for a particular use case. This class can then also do security controls, permissions checks, paramater verification and more.
Facade is just only one of aspects of implementations about user access control. In this thread
you,marc and crackajaxx have a good discussion about the object access control but not clarify the issue ,at least to me. If you can give more details about the acess control in the connections, we will be very happy. After all, the issue about acess control is very common in distributed system and worth paying more attentions.