> If you look athttp://pond1.gladstonefamily.net/errorrate.pngthen you > can see the sort of trending information that I collect. The big spike > was when google switched to 2.140g. The end of the spike corresponds > to when I changed my code to work better with whatever change they had > made in the 2.140g version. It also appears that the transition from > 180e to 184a roughly halved the number of errors that I am seeing.
Not sure what you're expecting anyone to do about it. It is not uncommon that one version of the API may silently ignore programming errors which another version doesn't. Examples of that kind of thing include : the use of string instead of number variable for coordinates, non-integer values for zooms, etc etc. To fix anything like that you need to look at the client side code, no amount of studying graphs of error logs against API versions will fix it for you. You've already described that process yourself in relation to 2.140g. -- You received this message because you are subscribed to the Google Groups "Google Maps 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-maps-api?hl=en.
