Been having probs again lately:
17:58:55 > Attempting connection over websocket
17:58:55 > Attempting connection over websocket
17:58:46 > Reconnecting in 10.0 seconds. Attempts: 2
17:58:41 > Reconnecting in 5.0 seconds. Attempts: 1
17:58:39 > Disconnected.
Topic: Clark moody sucking for anyone else? (Read 2989 times)
I glanced at the socket.io documentation and found what I needed to make the connection automatically reconnect after a disconnection. You should see messages in the Console at the bottom of the screen informing you of the progress of the reconnect attempts.
Let me know if the new code works for you. Maybe this refresh will be your last
Let me know if the new code works for you. Maybe this refresh will be your last
Seems to have worked. A+ cap'n.
lol yeah srsly
I don't know if it's the same update that triggered it, but if I turn group by price on I get nans. All through the order book.
Edit: only seems to happen on my Android phone (2.4); is fine on firefox. Has always worked before on the phone, so this is a recent change.
Edit: only seems to happen on my Android phone (2.4); is fine on firefox. Has always worked before on the phone, so this is a recent change.
hero member
Activity: 588
Merit: 500
Hero VIP ultra official trusted super staff puppet
Clark moody sucking for anyone else?
No, he exclusively sucks for me, because I pay him handsomely to do so.
I think what Clark's trying to say.... don't forget the BTC donation link on the website for this great improvement on an already-very-useful tool. 
I can breathe again!!! 
Yup, working much better here now
Just saw the script reconnect. Works like a charm.
I scrolled back through my console output and saw four reconnects - no more reloads!
This is a big development for the site, and I'm glad it finally happened. Thanks for kicking my butt into gear with this thread.
I can breathe again!!!
Yup, working much better here now
The periodic disconnect is due to mtgox killing the process in a cron job. They have to do this because apparently there's an open bug in the socket.io implementation that leaks resources and it hasn't been fixed yet.
I was wondering why I no longer had to reload. Seems to be working great to me.
(Update)
Just saw the script reconnect. Works like a charm.
(Update)
Just saw the script reconnect. Works like a charm.
Sweet, thanks for the constant development Clark.
I glanced at the socket.io documentation and found what I needed to make the connection automatically reconnect after a disconnection. You should see messages in the Console at the bottom of the screen informing you of the progress of the reconnect attempts.
Let me know if the new code works for you. Maybe this refresh will be your last
Let me know if the new code works for you. Maybe this refresh will be your last
Awesome! good looking out Clark. The connection automatically reset for me at 7pm est.
I glanced at the socket.io documentation and found what I needed to make the connection automatically reconnect after a disconnection. You should see messages in the Console at the bottom of the screen informing you of the progress of the reconnect attempts.
Let me know if the new code works for you. Maybe this refresh will be your last
Let me know if the new code works for you. Maybe this refresh will be your last
I will be looking into the socket.io documentation a little more closely to see if I can't force the connection to restart when this disconnect behavior is detected.
I agree that having to refresh the page every so often is pretty lame. It reflects poorly on my site's reliability, even though the real time data stream is controlled by Gox.
I agree that having to refresh the page every so often is pretty lame. It reflects poorly on my site's reliability, even though the real time data stream is controlled by Gox.
That's what I started to figure towards the end. Oddly I had to restart to get it to work again. Socket connections can be a real bitch.
I will be looking into the socket.io documentation a little more closely to see if I can't force the connection to restart when this disconnect behavior is detected.
I agree that having to refresh the page every so often is pretty lame. It reflects poorly on my site's reliability, even though the real time data stream is controlled by Gox.
I agree that having to refresh the page every so often is pretty lame. It reflects poorly on my site's reliability, even though the real time data stream is controlled by Gox.
Yep, its gone downhill. 
Just go to btccharts.com. They're pretty awesome nowadays.
http://www.btccharts.com/?dark;volumeon
http://www.btccharts.com/?dark;volumeon
Sometimes runs for hours ok, other times it freezes almost as soon as it loads
Jump to: