Catálogo de publicaciones - libros

This chapter gives you a look at Zope’s security architecture. Security is crucial to most web applications, especially when they are exposed to the Internet. This discussion has been postponed until now for two reasons. Firstly, we wanted to get started on the example application without having to worry too much about security initially. Secondly, understanding the security system requires an understanding of how Zope itself works. For example, understanding the concept of a trusted adapter requires an understanding of the fundamental concept of an adapter.

In the last chapter we discussed how users (known as principals) interact with Zope’s security system. In this chapter we look at how users are authenticated.

No software is bug-free. In fact, a great part of a software developer’s time is spent finding and fixing bugs. The more complicated a system gets, the more complicated it usually is to find and fix bugs. Fortunately, Zope provides tools to help you debug Zope-based applications. They are introduced in this chapter.

Our global community web application for hobbyist cooks is now complete. In earlier chapters we built a website for sharing and storing recipes. The web application also now supports several Internet protocols, data formats and authentication schemes. This chapter looks at packaging the application and deploying it on a production server.