Update: We've posted answers to the common questions that developers have been asking here: http://groups.google.com/group/google-maps-api/web/map-indexing-faq
Please keep in mind that this is an early experiment and we plan to iterate and improve it over time. Thanks for all the interest and questions. - pamela On Nov 27, 3:00 pm, "pamela (Google Employee)" <[email protected]> wrote: > Hey developers- > > Just wanted to let you know that we've seen all your questions here, > and are working on a set of answers for you from the API team. > > - pamela > > On Nov 25, 2:25 am, Mike Williams <[email protected]> wrote: > > > > > Wasn't it Joe Edelman who wrote: > > > >My app opens and live-updates infowindows based on real-time streaming > > >data coming in through polled or long-running requests. It's already > > >unusually bandwidth and CPU intensive for javascript. The idea of a > > >many additional xhrs or fetches to google while this is happening > > >seems like a bad one. Am I right? Should I opt out even though I > > >don't mind being indexed? > > > There would appear to be nothing to be gained by having your infowindow > > content indexed if the content will have been be replaced by different > > data by the time someone follows the link to your page. The only thing > > you lose by switching indexing off is getting page hits from people who > > are looking for stuff that you used to have in your infowindows but > > probably don't any more. > > > -- > > Mike Williamshttp://econym.org.uk/gmap -- 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.
