This is purely guesswork but given that waves are extensively client- side driven, and that the current push model can not physically push contents onto static resource (IE: stream/poll aren't natively implemented), it's most likely going to be a no (unless the crawlers can parse javascript). However, it's possible to poll the resources on the serverside and render it in a indexable, non-realtime fashion to the client, however that defeats the purpose of wave.
Of course, my knowledge is limited so it might be better for one of the brilliant google employee to delve further into this problem. I don't know, Google's been known to come up with solutions to ideas traditionally thought to be impossible to implement (taking wave for example) On Nov 7, 6:30 pm, Danny Tuppeny <[email protected]> wrote: > Apologies if this has been asked before, but I can't find any info on > it... > > Embedding waves in a blog looked pretty cool, but my impression (based > on nothing but the video of the I/O demo) is that it's all Javascript- > based. This makes me wonder whether Search Engines would be able to > read any content embedded in a blog this way? Is there a server-side > embed API that would allow the current wave to be output in a way > search engines can index it? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Wave 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-wave-api?hl=en -~----------~----~----~----~------~----~------~--~---
