SignalR/SignalR — pull request #963 by kppullin (2012-11-14 02:26:44+00:00)
Title: Don't emit the UTF8 BOM in the response stream

By default, a `StreamWriter` opened with `Encoding.UTF8` includes the UTF 8 byte-order-mark, which causes issues with consumers that don't expect it (Java & Node.js apps being a couple examples).

The proposal here is to *not* include the UTF8 BOM with the response, in order to make life easier on consumers (like `hubot-jabbr`), which fail upon reading the BOM. This also saves an amazing 3 bytes!

Another minor benefit is that this brings consistency to `PersistentConnection`, `ForeverTransport`, and `LongPollingTransport`. `PersistentConnection` doesn't send the BOM, while the other two do.