In the former article of the series We rendered the user interface of our widget inside an anchor element in publisher’s website; We asynchronously loaded widget styles; We implemented a very naive authentication mechanism. We also defined a job queue _wdq (similar to google analytics’ _gaq) to be able to …

In the recent post, we’ve seen how to implement error handling with our JSONP requests, using o2.JsonpController, and o2.JsonpState objects. The article was a little lengthy, and I thought it’d be nice to summarize the usage with a quick code exampe:

We will soon finalize our Mobile JavaScript Application and convert it to an Android-market-ready .apk file. But before that we’ll need some enhancements to our o2.Jsonp object. o2.Jsonp, which allows cross-domain communication using JSON with Padding, was first mentioned in this post. You can click here, to get the source …

The Problem While working on our JavaScript mobile chat application, we will be constantly listening to open Comet connections. It’s possible that, the server we are listening to may not respond in a timely manner, due to traffic overload or due to some external factor such as a slow network …