I understand that. KmlLayer has obvious disadvantages, some of which i ecountered with uri length problem. And FusionTablesLayer, well it says in developer guide that it is experimental stuff - so good for playing and testing, but not for production, i would say.
On Tuesday, March 6, 2012 11:12:10 PM UTC+1, [email protected] wrote > That is all a matter of the processing power and browser you are > using. Client-side parsing works OK for powerful modern machines > running modern browsers. > > Server-side tile generation (KmlLayer/FusionTablesLayer) will be > better for large data sets on older computers/browsers or mobile > browsers. > > Larry -- You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-maps-js-api-v3/-/RP3nMvzZyMgJ. 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.
