I'm doing this review in two parts because the opening and closing chapters of this book are vastly different from the rest.
I have to admit to wondering, when I was first asked to review this book, exactly what the market was that it's aimed at. After all, aren't all domino developers heading towards XPages now? Could a book on "traditional web programming in domino" still be relevant today?
Well, surprisingly it is.
The opening chapters deal with issues and requirements that our developers and I still constantly struggle with . They cover version control, issues logs, staging servers, commenting/documentation, standards and the big killer "scope creep". There are sections on using the "champions" in your office to drive projects, maintaining consistent URLs and setting up a developer test environment.
The last two chapters of the book cover Security, Performance, Testing and Debugging. Again, these are mostly high-level. The security sections discuss planning for security, ACLs, reader and editor fields, the problems of hidden fields and sensible additions such as edit prevention after approval and logout facilities. The performance sections discuss archiving, code optimisation and the measurement of response time. The testing and debugging chapter talks about the requirements and limitations of user-testing and suggests various ways this testing could be improved. There are also some great sections on debugging which will help those new to domino to track down issues in their applications.
The book is available from Packt Publications.