Hi, So what we changed lately is that we removed the support of the original _undocumented_ protocol that was used before last November, when we published the protocol. So its not that we removed a support for some documented feature, and broke some thing that should be backward compatible. In addition, this change was in the test servers for a few days.
So now the best approach will be to read the documentation about the current format of the request and response, and making sure you are using a valid notation. Even if there will be new versions, this one will not break. Again - Note that the changes are: reqId instead of requestId c: for the rows use of words instead of single letters for column types. Regards, VizGuy On Tue, May 12, 2009 at 1:57 AM, BT <[email protected]> wrote: > > Dear Google-- > > Please notify the user group of imminent JSON representation changes > before making them. > > We noticed that the c: prefix was recently introduced for the JSON > representation of DataTable rows. This silently broke our chart code > when we initialized DataTables using its constructor with a string > argument. There was no parser error message. Better to fail noisely. > > Thank you. > > Bishr > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Visualization API" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/google-visualization-api?hl=en -~----------~----~----~----~------~----~------~--~---
