grahamscott/pusherrestdotnet — pull request #4 by jewer (2011-12-15 17:50:18+00:00)
Title: For anyone trying to push behind a firewall or proxy...

Hey, I needed to start pushing messages behind a corporate firewall, and noticed there was no way to get around the proxy in the current implementation. This commit is a simple, un-unit-tested way of setting the proxy. The ctor argument is optional so it wouldn't change anyone's current functionality.

Unfortunately, given the current structure, it's pretty impossible to write a unit test to validate that the web client's proxy is set with the provided argument. Not sure what the direction is for those tests, but I'd be happy to volunteer a little time if you were willing to restructure your code a little bit to provide some tests re: the collaboration between PusherProvider and whatever is making the actual HTTP request.