Comment 3 for bug 851691

@Scott: the feature was planned earlier, but put on hold before the feature freeze because of server availabiliy issues. By that I mean: the HW was not ready.

The feature has been re-prioritized as the server issues have been resolved and because of the business aspects of course. We reprioritized the end of the development because of the revenue implications associated with it.

From a technical point of view, I think we have made our job in finalizing the development, testing it with the staging server, ensuring error cases are handled gracefully, taking latency problems into account (async calls). That helped us solve a rather nasty bug in the process: (bug #76761)

John will comment on the test results for the server side.