Fortunately, this is not difficult as we will see in chapter 6.
As Zend_Acl is an implementation of the Role Based Access Control List system, the manual talks in lots
of abstract terms. This is because RBACL is a generic system that can provide access to anything by anyone
and so specific terms are discouraged. Hence we talk about Roles requesting access to Resources. A Role is
anything that may want to access something that is under the protection of the Zend_Acl system. Generally, for
a web application, this means that a Role is a user that has been identified using Zend_Auth. A Resource is
anything that is to be protected. This is generally a record in a database, but could equally be an image file
stored on disk. As there is such a wide type of resources, the Zend_Acl system provides for us to create our
own very simply by implementing Zend_Acl_Role_Interface within our class.
Internationalization Components
As we live in a multi-cultural world with multiple languages, the framework provides a rich set of functionality
to allow for localizing your application to match your target users. This covers minor issues like ensuring that
the correct currency symbol is used through to full support for changing all the text on the page to the correct
Licensed to Menshu You
Pages:
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31