如何使用rspec测试Thinking Sphinx delta索引(How to test Thinking Sphinx delta indexes using rspec)

 我不确定上述评论的目的是什么 - 这个特殊问题对我来说似乎很清楚（也很常见）。 
 
 谷歌现在可以做很多事情来索引JS应用程序，但大部分都试图对延迟加载的内容敏感。 今天有许多站点将注释流，侧边栏小部件，有时甚至是主要内容等内容加载到空页面shell中作为单独的资源。 如果没有具体说明他们做了什么，Google暗示的是他们现在非常擅长处理这类事情。 
 
 这并不意味着他们将真正运用您的应用程序，而在SPA中，风险非常高，他们不会发现您希望他们做的所有事情。 这是一个架构问题，您需要回到您的数据模型，您比其他人更了解。 最好的结果将来自使用服务器端代码（通常在批处理作业中）从原始数据模式生成sitemap.xml。 您可以生成您知道应用将响应的所有网址，并将网站地图设置为准确反映您希望将应用编入索引的方式。 
 
 然后，Google可以点击每个页面，您需要做的就是确保这些页面无需进一步交互即可运行。 这样他们就不必在应用页面中跟踪链接。 

I'm not sure what the purpose of the above comment is - this particular question seems pretty clear (and common) to me.
 
Google can do a lot to index JS apps now but most of it is trying to be sensitive to lazy-loaded content. There are many sites today that load things like comment streams, sidebar widgets, and sometimes even primary content into an empty page shell as a separate resource. Without making specific statements about exactly what they do, what Google has implied is that they're pretty good at dealing with this type of thing now.
 
That doesn't mean they're going to actually exercise your app, and in an SPA the risk is very high that they won't discover everything you want them to do. This is an architectural problem that you need to take back to your data model, which you know better than anybody else. Your best result is going to come from using server-side code (usually in a batch job) to generate a sitemap.xml from your raw data schema. You can generate all the URLs you know your app will respond to and set the sitemap up to accurately reflect the way you want your app indexed. 
 
Google can then hit each of those pages, and all you need to do is make sure that when they do, those pages will work without further interaction. That way they don't have to follow links within the app pages themselves.