是否存在现有的“通过 CDN 的 Silverlight 程序集”？类似于 Google/Microsoft 如何提供 jquery 的选项？
我在 javascript/jquery 工作中真正怀念的一件事是能够通过 CDN 将主要部分（jquery、常见插件）提供给客户端。它有很多好处（托管成本、启动时间、跨应用缓存等）
似乎所需的繁重工作已经由 Silverlight 对应用程序库缓存的支持，至少在以下方面：可以“自动”完成。我想 CDN 只需要一个 clientaccesspolicy.xml 允许它，并且可能对应用程序库缓存支持进行一些更改，以便它可以查看支持库的 xap 源以外的地方（尽管可能已经存在，我只是还没有找到吗？）。
当然，我可以采用我的程序集并执行“手动”方法（将它们上传到 S3 或其他地方），但假设我使用库的“标准”构建（MVVM Light、Caliburn.Micro 等），看起来这对于 Silverlight 应用程序来说将具有与现有 CDN 对 jQuery 应用程序相同的社区范围的好处。
这已经是一个已经解决的问题了吗？如果是这样，执行此操作的项目/代码在哪里？ ：）
谢谢！
One of the things I really miss from javascript/jquery work is being able to have major pieces (jquery, common plugins) served up to the client via CDN. It has lots of benefits (hosting costs, startup time, cross-app caching, etc.)
It seems like the needed heavy lifting is already in place with Silverlight's support for Application Library Caching, at least in terms of something that could be done 'automatically'. I'd imagine the CDN would just need a clientaccesspolicy.xml allowing it, and likely some change in the Application Library Caching support for it to look at places other than the xap source for the support libraries (although maybe that already exists and I just haven't found it?).
Certainly I could take my assemblies and do a 'manual' approach (upload them to S3 or somewhere), but assuming I'm using a 'standard' build of a library (MVVM Light, Caliburn.Micro, etc. etc.), it seems like this would have the same kind of community-wide benefit for Silverlight apps that the existing CDN's have to jQuery apps.
Is this already a solved problem? And if so, where's the project/code that does so? :)
Thanks!
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我相信在应用程序库缓存开发的早期阶段，Microsoft 会提供一些通用库 zip 的概念。然而，由于某些未公开的原因，这个概念并没有出现在发行版中。应用程序库缓存仅适用于原始源文件夹。
这听起来是个好主意，但我认为没有任何立足点。当有大量网站使用通用 CDN 时，CDN 概念就有效。 Silverlight 在许多网站中的使用还不够广泛，因此即使对于最常见的 SDK dll，CDN 方法也没有真正的价值，更不用说第三方 dll 了。
I believe in the early stages of the Application Library Caching development there was to be some concept of Microsoft delivering common library zips. However for some undisclosed reason this concept did not make it in to the release. App Library Caching only works from the original source folder.
It sounds like a nice idea but I don't think has any legs. The CDN concept works when there is a large body of websites using a common CDN. Silverlight just isn't in enough common use amongst many web sites to make a CDN approach really worthwile even for the most common SDK dlls let alone the thirdy party dlls.