Timeout when sending to Growl 2.0 when including binary data about gntp HOT 1 CLOSED

As Falkenberg brought up in IRC, need to make sure there's a double crlf after EACH data block. Need to make sure to write a test case around these scenarios so I can get it right.

if you start supporting instances where there would be more than one (icons for notifications during
registration for instance, which 2.0 should support), that would still fail, the first read would go looking for
a double crlf, and not find one till the end of the headers for the next data block, and fail due to that data
block being seemingly too long

from gntp.