This code occasionally will raise a "ConnectionClosedException" when streaming depth updates (I assume thereby creating a zombie thread). It then creates a new thread and attempts to connect again. This process continues until eventually it segfaults. Any chance you have any updates to this code or ideas on what needs to change to deal with the MtGox disconnects? Has MtGox said anything about mitigating the disconnects?
Many thanks, no matter, for mostly working code--it was a great kickstart.
Many thanks, no matter, for mostly working code--it was a great kickstart.
I am curious about fixes for the "ConnectionClosedException" as well. Currently I just catch it as an exception and then reset the state of my app so that it keeps running, but I would like to see a better OOP way of handling this.
