TODO

NEXT-TAG
========

Short-list for the next TAG:

- Verify slides and the book for empty pages.

Content
=======

- Introduction: Explain the course language early. This could also include
  markup used (e.g: ``literal`` stuff etc).
- Split the introduction to Varnish sub-chapter into introduction to the
  FOSS-project and introduction to Varnish the software.
- Mention VTLA's wherever relevant. This might be an appendix too.
- Find a unified approach for Vary. There are at least two or three places
  it's discussed.
- VCL: Need to re-phrase the state engine talk. Specially regarding what
  state is next.
- Introduction to the test environment
- In getting started: Start out early by describing:
   - Brief discussion on the test setup.
- On install: Mention how to find VCL syntax errors on rhel
- Go over tools (specially sizes/hist?)
- The VCL Functions chapter needs an overhaul
- Cache Invalidation: Banning needs work. Add cache channels.
- ACLs: Generally fix.... List of suggestions from phk:

  - Other things about ACL:  you can use domain names:
    "www.cnn.com" / 24
  - If you put an entry in (...) it ignores it if DNS
    does not resolve.
  - Also IPv6
  - Blindingly fast, long lists are perfectly OK.
  - Good place to show example of "include" in VCL

- Loadbalancing

  - More examples
  - Need a new exercise.

- Add more visuals for the VCL chapters
- Use article.php and httpheaderexample.php-like approaches more. Both for
  webdev AND the rest.
- VCL functions: Need more examples.
- NUKE the tools chapter, or move it to a more complete Appendix.

Webdev-related content
======================

- Fix date-references in php-code
- The exercise-code for the web-dev material should be more accessible.
  It's currently included in an appendix that's never included anywhere.
- Distribute it in a tar-ball?

Technical
=========

- Formalize style practices
- Unify the style of the new and old chapters
- Go through the various util/ stuff to see if I missed any tools
- The PNG used for the flowchart looks bad in the PDF.
- Amazon-instances need to configure apache2 and php.
- Check if we can use -b1 instead of -b2 for the non-slide PDF, so we don't
  waste so much paper.
- Better PHP regression tests
- Probably also want better test for the VCL
- Possible to test bans?
- Make distdist == scp and formulate Announce-mail.
- Automate fetch default VCL from Varnish
- Verify fonts
- Reduce number of blank pages
- slide-only class, to allow content to go over multiple slides without
  resulting in multiple empty pages in the printed version
- How do we build the graphics that Jerome provided? :D They look
  proprietary.