You might look into a library like Mapstraction, which abstracts on top of the various Maps APIs, so that you can easily switch if something horrid was to happen to one of them (or if their terms changed). OpenLayers is also an option, as it wraps the Google Maps API and its own native API.
- pamela On Apr 26, 3:29 am, "neil.young" <[email protected]> wrote: > marcelo schrieb: > > > Solo, > > >> anyway, im wondering how you succeed to compare business with world > >> existing. > >> you can make agreement with company but with planet, its little harder > >> i think :) > > > It may be a little harder with the planet, but it is the same logic. > > 6 months ago, you wouldn't have imagined that GM or Chrysler could go > > bankrupt, but today they are on the edge. > > You cannot guarantee that Google will continue to exist, or that the > > Maps API will continue to be supported, though it is likely that they > > will. > > >> P.S sorry, its sunny here in my village and you push me to make jokes, > >> thank you for that.. > > > Enjoy the Croatian sun! ;-) > > ...and all this has certainly a lot to do with the Google Maps JS API. > > Thanks for sharing --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
