> It captures AJAX requests which were made while the connection was down, and remakes them when it's back up, so your app reacts perfectly.<p>Is this something I want as a user? If an app seems to be offline, I tend to do various things just to check or re-establish connectivity. Say, hit the Send button a few times, order columns, filter, search, whatever. Stuff, I wouldn't do if I had connection.<p>Once the app reconnects, all this nonsense would be executed. I'm not so sure if I'd really want this as a user.<p>This leads to the question: How fast does it notice that the app went offline? Do I get the chance to do stupid things as a user or will I be shown the "you're offline" message soon enough?
You guys have put out some great pieces of JS in the last year and the quality is getting better. I'm a big fan of how this is not jQuery dependent and the code is simple. I've been watching the HubSpot repos since globalMessenger and the code and presentation are far above par.<p>Thanks for releasing your internal libs.
I think this is a neat proof of concept. However, you have to be extremely careful to not get out of sync hell.<p>I see an enormous load of extra complexities for what seems to be very little advantage.<p>On the other hand, if you list all the queued non-GET AJAX call for the user to resend manually, it could be good.<p>I'm ambivalent :(
This comes at the perfect moment for me: I'm building an inventory web app used in warehouses on tablets and I'm faced with connectivity issues (incomplete or fluctuating WiFi coverage for instance).<p>Making the app less prone to these issues is certainly going to help build something more robust, so thanks a lot!
The more I look into HubSpot libraries, the more I am amazed by their approach. To the point, small and flexible. And if the only annoyance people can bring up is a snake game, then you should be proud :)<p>Regarding this particular module: is there any chance of combining this with a websocket connection (particularly socket.io)? I don't really care much for off-site requests, but notifiying the user of a disconnected socket would play well into this.
This is actually a very cool idea, but I'm gonna raise a minor nitpick which has been growing inside me over the last few months:<p>> It has a number of beautiful themes and requires no configuration<p>"Beautiful" is a word that's really getting overused nowadays, and I cringe whenever I see it.<p>Edit: I anticipated the downvoting
This is just what i need!! For my html5,json,localstorage app.
But what if the user press Reload ?
But what if the browser crasher or closed normally, does the buffer stay ? if not then it's useless!