Hey all,

I've been working in the last 3 weeks to clean up our social api code and
restructure it to cleanly implement the json-rpc protocol. Since we're
getting close to release date it seemed important to make sure all our
internal interfaces and class structures made sense and were clean and
consistent.

Work has been a bit slower then desired, due to my doing my rounds at the
google developer days here in europe (the upcomming commit will have been
written in 6 different countries, a personal record for a single patch :)
but I've got some time the next 2 weeks to finish it & some other todo
items, so I expect the patch to land 'soonish' (probably near the end of
this week).

This does mean the params, param order, return values and some class
structures of the social interfaces have seen some change, which will break
your current code ... a complete pain in the backside i know, but if we
don't clean up before release, we'd probably be stuck with a messy interface
for a very long time; So I thought it was worth the short term pain for the
long term benifit.

Also if some people are wondering why some issues and patches haven't been
solved & applied, it's for this very same reason, I want to land this big
patch before I can rework & apply those to the new code layout; So don't
think their forgotten or ignored! I'll get to them as soon as the json-rpc
implementation & social code cleanup has landed.

  -- Chris

Reply via email to