AJAX、服务器推送实施问题
我对整个 AJAX 的处理方式比较陌生，所以如果我将两种不同的东西混合在一起，请原谅我（尽管如果您能对此发表评论，我将非常感激）。 我的问题是这样的： 我有很多 Web 客户端（假设大约 1500 个），我希望它们在启动时使用某种 ID“订阅”Web 服务器，然后我希望 Web 服务器（APACHE）向它们发送相关的 url（动态构建不会）对于这个目的来说并不重要）显示（某种重定向）。 现在我的问题基本上是我在过去的几天里阅读了很多关于如何做到这一点的文章和指南，我认为我有太多的流行语。 我认为为了解决我的问题，我需要某种称为“延续”的 COMET 实现（以支持许多客户端）。这是正确的吗？ 我走的路正确吗？ GWT 与此有任何联系吗？
提前非常感谢大家
编辑：阅读更多内容后，我认为基本上 Java Servlet 3.0 异步支持正是我在服务器端所需要的（如果我错了，请纠正我），并且我仍在客户端上争论边？也许 GWT 到底？ 谢谢
I'm relatively new to the whole AJAX way of doing things so please excuse me if I'll mix two different things (although I'd appreciate it greatly if you could comment me on that).
My question is this:
I have many web clients (lets say around 1500) whom I want when starting up to "subscribe" to the web server with some sort of Id and then I want the web server (APACHE) to send them a relevant url (build dynamically doesn't really matter for this purpose) to display (sort of redirect).
Now my problem is basically that I've spent the last few days reading a lot of articles and howto's on how this should be done and I think I have too many buzz-words.
I think that in order to solve my problem I need some sort of implementation of COMET with something called "continuations" (to support that many clients). Is that correct?
Am I going down the right path?
Does GWT have any connection with this?
Thank you all very much in advance
EDIT: After reading some more I think that basically the Java Servlet 3.0 Asynchronous support is exactly what I need on the server side (correct me if I'm wrong) and I'm still debating on the client side? Maybe GWT after all?
Thanks
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
好吧，我之前确实搞得一团糟，所以我把它放在那里，这样我的废话就不会让任何人感到困惑。
我正在寻找的是服务器端的异步请求支持，涉及允许许多用户和可扩展性的线程处理，以及客户端的异步请求支持，以方便使用 Comet 模式。
我发现 Jetty、Tomcat 和 Grizzly 都为此提供了解决方案（只需使用 Comet 搜索特定服务器并查看它们提供的内容），但我决定使用 Glassfish 中支持的 Servlets 3.0 规范，尽管它只会与 Java EE 6 一起发布，以免受限于特定服务器。
在客户端，我可能会因为许多与 Comet 无关的其他原因而选择 GWT，因为它对 Comet 有足够的支持。
谢谢
OK, so I indeed was making a bit of a mess earlier and I'm putting it out there so my nonsense doesn't confuse anyone.
What I was looking for was asynchronous request support both on the server side, regarding the thread handling to allow many users and scalability, and on the client side for ease of use of the Comet patter.
I've found that Jetty, Tomcat and Grizzly all offer a solution for this (just search the specific server with Comet and see what they offer) but I've decided to use the Servlets 3.0 spec as supported in Glassfish even though it will only be released with Java EE 6 as to not be tied down to a specific server.
On the client side I will probably go with GWT for many other reasons not related to Comet and because it has sufficient support for Comet.
Thanks
您可能想尝试 StreamHub 推送服务器 和随附的 GWT Comet 适配器。这将为您提供可扩展的 Comet 服务器和 GWT 客户端。
You may want to try StreamHub Push Server and the accompanying GWT Comet Adapter. This will give you a scalable Comet server and a GWT Client-side.