> I guess I don’t quite understand the distinction between static and > dynamic as it is used here.
What they're trying to distinguish between is - "I have no idea what the address is until the user types it into some form." Since that's going to be client-side, handling the geocoding client-side too would be smart. That also allows a "did you mean? are you sure? would you like to move it a bit?" functionality, which sounds like what you need. Example - http://maps.huge.info/pinpointaddress.htm and "I have a collection of addresses already on my server e.g. database" Whilst it would be possible to send the address to a client upon every access to e.g. work out the nearest one, its obviously smarter to work through the database and geocode each address at the server ONCE and store the result. Hence the provision of an HTTP geocoder too. In your original post you talked about processing in php, which would otherwise require use of this, but if your data is going to be pre- processed at the point of entry before getting this far ... you won't need it. -- 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.
