TODO

1. Check out whether we can support Qpid
2. (Dependant on 1.) implement an amqp namespacing feature so that bundles of generated code can be plugged at runtime and mixed, i.e. conmsume from RMQ and publish to Qpid, etc. [done in auto-load-able branch]
3. Write some sensible unit tests. This may be a bit challenging, as any meaningful test will want to act as both consumer and producer. Can't use pcntl/forking as this seems to screw up the PHPUnit / Xdebug code coverage feature.
4. Unify the 2 branches by introducing a build system. Ideal would be to split the API classes in to single class files (as in the auto-load-able branch) and have the build system capable of outputting to either a class-per-file or namespace-per-file output. Most likely candidate that I know of the moment: Phing.
5. Look again at the runtime performance of the generated code. I think there could be a faster way of parsing the wire-level messages by using a single call to pack() and unpack() rather than requiring a single method call per Amqp field.
6. Split RabbitMQ-specific features out in to subclasses.