Hi, Sorry for taking a bit to respond. There's actually no contradiction between what I wrote in my blog post and what Ben wrote. The JS geocoder is meant primarily for use in the JS API. So we wrote it in such a way that it would be most efficient for that purpose, and give you the best performance. To create an additional JSON output would bloat the code a bit.
That said, there's nothing wrong with taking some of the properties you get and sending them to the server for processing. It's not the primary focus of the JS geocoding API, but it is a use case we support. Mano On Mar 25, 12:02 pm, Sheepz <[email protected]> wrote: > I did eventually do that, and I understand what you're saying about > the majority of user and accept it, however my point from the begining > was that the problem is that we have two methods together here, if > users usually prefer js object, then why not make the entire structure > a js object? Perhaps there isn't a right answer here and maybe it's > just me, but I feel that when a response object is received it should > be either all js or all json, the way it is now imho just makes it > harder for people like me who prefer it jsoniez and for people who > prefer it jsed... > > I appreciate the responses and their promptness, keep up the good > work! > e. > > On Mar 25, 2:24 pm, Chad Killingsworth > > > > <[email protected]> wrote: > > > about the second comment, I'm sorry but i don't understand, you're > > > saying that the V3 API 'promotes' the json objects to be JS objects? > > > what for? why not keep it as json and if need be, the js developers > > > can 'promote' it on their own. > > > Because almost every use for this requires an actual JS object. Why > > force the majority of developers to create a LatLng object? > > > I believe your root issue is that the LatLng object serializes to > > something you can't use. Instead of using JSON.stringify, why not > > create your own function to walk through the returned data and create > > a proper JSON string. The function wouldn't even be that complex. > > > Chad Killingsworth -- You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" 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-js-api-v3?hl=en.
