On Aug 17, 4:40 am, <[email protected]> wrote: > > but it apparently involves caching & cookies for data storage & retrieval on > the client.
Cookies are just a way of transmitting data from the server to the client. You could just as well send the information in plain text via an AJAX call. The advantage of using cookies is that you only transmit what you need together with each tile and no more, but the disadvantage is that many people do not normally accept cookies. (myself included). > It also seems to rely on constant 'mousemove' listening in order to detect > whether the cursor is in the proximity of a 'pseudo-marker'. > Im not sure this is the best way to go...seems suspicious... What alternatives can you think of? :-) You don't have DOM objects, (such as marker images), where to detect a click and associate it with an id, so you need to know where the mouse is. If you want onmouseover functionality then you have to track the mouse. If you only want click functionality then you can scan your data once the click has occured. -- Marcelo - http://maps.forum.nu -- --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
