Be careful with this though, as it could potentially be dangerous if done incorrectly, since cookie data can be forged. You would then create an adapter (discussed shortly) to authenticate against cookie data. For example, if you wanted to “remember a user” in between sessions, you could create a storage class that writes identity data to a cookie. To create some other storage method, you simply implement the Zend_Auth_Storage_Interface interface. This class, in turn, uses the Zend_Session component, which is essentially a wrapper to PHP’s $_SESSION variable (although it does provide greater functionality). Zend_Auth provides the Zend_Auth_Storage_Session class for this. ■ Note It is possible to write custom storage methods, but the most common storage method will arguably be in a PHP session. Books are supposed to provide added value to these APIs and examples to make the topic That makes me question the reviewers who say the examples are clear and concise − the examples on the web already do that. Examples are not what I care about as much as the rich and deep information because there are many examples already on the web − no point acquiring the book just for those alone. So if I'm going to buy a book on PHP and XML, I expect that it will provided added value information as well as design decisions, business concerns and best practices. Personally, I think many of these concepts can be learned in PHP in about 2−3 days of trying the APIs out if you already know a great deal of XML. The problem is that the reviews already here have so much fluff that they didn't even begin to describe themselves, thus they could be ambitious or lazy, smart or dim, and hobbyist or entrepreneurs. I think it's pretty safe to assume that this book is good for some people and bad for others. I'd present a true review − one from an actual reader rather than from someone else.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |