improve commandstream for large/many messages

Squashed commit of the following:

commit 43eda4249f679b40435c504169ae712919626fe6
Author: jeffrom <jeffmartin@gmail.com>
Date:   Sun Mar 30 14:35:25 2014 -0700

    add undefined test for templateloader

commit 18b230b5778b74b01c3eb2c89ca17d0727458b64
Author: jeffrom <jeffmartin@gmail.com>
Date:   Sun Mar 30 05:35:57 2014 -0700

    fix protocol transform stream for large requests

    it wasn't triggering the callback for the next chunk because it was
    waiting for the message to be complete. the callback should be used when
    the chunk data has been consumed, not processed

commit 53a38fd739f75cd417da9b6c8fdb60bc128a4096
Author: jeffrom <jeffmartin@gmail.com>
Date:   Sun Mar 30 04:38:45 2014 -0700

    checkpoint

commit 78907cd0cd6b300d9158227f9dc782993db269da
Author: jeffrom <jeffmartin@gmail.com>
Date:   Sun Mar 30 01:37:35 2014 -0700

    many changes around error handling/response logic

    fix infinite loop case when client sends incomplete request
    dont prematurely reset a commandstream object
    debug print a parseMsg'd command
    simple parseResponse for a js client (testing only for now)
    pass protocol errors back to the client
    redo a bunch of testlib
    add large message test

commit 7dcbca31d43e7366fb1937dab8f4126e254cba49
Author: jeffrom <jeffmartin@gmail.com>
Date:   Sun Mar 30 01:35:28 2014 -0700

    ignore some stuff