Thanks Pamela. As I said in the other thread, I'm not complaining but
just trying to come with ideas to help avoid another problem.

I think hard-coding to a version is a very good solution.  The current
version of 2.s was released over a year ago which means that
developers can limit their upgrades to quarterly, for example, and not
have to worry about being hurried into a new API release.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to