I am in a similar boat with some clients that utilizing the flash API, I was fortunate enough to tell them they would need to switch to javascript in the future. While it would take some work, I could move to another flash based API within the application. If the client is blaming you for something Google did, I am pretty sure you don't want that client anyways.
Also comparing a back-end server language is not the same as a connected online API. If you read through bing's map TOS it reads almost identically to the Google TOS. They can cancel services, they are not liable etc.. etc.. Also in scale of course asp.net would have higher quality support then the flash maps api, in the same way the google javascript API has better support, it's about resources. I am pretty sure if you're using a microsoft product that very few people use, you're not going to get the same quality of support as you would with asp.net. I haven't done any form of bench marking yet, but V3 seems fast. Also here is a link to the article http://money.cnn.com/2011/09/20/technology/microsoft_bing/index.htm It sucks you lost a client, however I would be hesitant of judging Google based just on the flash maps API depreciation. It's a big company, not everyone at it decided they wanted to depreciate the flash maps API. -- You received this message because you are subscribed to the Google Groups "Google Maps API For Flash" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-maps-api-for-flash/-/o6cTyU-pQR8J. To post to this group, send email to google-maps-api-for-flash@googlegroups.com. To unsubscribe from this group, send email to google-maps-api-for-flash+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-maps-api-for-flash?hl=en.
