SSE和Servlet 3.0

nim*_*o23 16 html5 servlets server-sent-events

我在页面加载时注册了典型的SSE:

客户:

sseTest: function(){

var source = new EventSource('mySSE');
source.onopen = function(event){
console.log("eventsource opened!");
};

source.onmessage = function(event){
var data = event.data;
console.log(data);
document.getElementById('sse').innerHTML+=event.data + "<br />";
};
}
Run Code Online (Sandbox Code Playgroud)

我的Javascript-Debugger说,"eventsource已经打开了!" 成功了.

我的服务器代码是一个Servlet 3.0:

import java.io.IOException;
import java.io.PrintWriter;
import java.util.Random;

import javax.servlet.ServletException;
import javax.servlet.http.HttpServlet;
import javax.servlet.http.HttpServletRequest;
import javax.servlet.http.HttpServletResponse;

@WebServlet(urlPatterns={"/mySSE"}, name = "hello-sse", asyncSupported=true)
public class MyServletSSE extends HttpServlet {

@Override
public void doGet(HttpServletRequest req, HttpServletResponse resp) throws ServletException, IOException {

resp.setContentType("text/event-stream");
resp.setCharacterEncoding("UTF-8");

Random random = new Random();
PrintWriter out = resp.getWriter();

//AsyncContext aCtx = req.startAsync(req, resp);
//ServletRequest sReq = aCtx.getRequest();

String next = "data: " + String.valueOf(random.nextInt(100) + 1) + "\n\n";
//out.print("retry: 600000\n"); //set the timeout to 10 mins in milliseconds
out.write(next);
out.flush();
// do not close the stream as EventSource is listening
//out.close();
//super.doGet(req, resp);
}
}
Run Code Online (Sandbox Code Playgroud)

代码有效!Client-Code每3秒触发一次doGet() - Method并检索新数据.

问题: 但是,我想知道如何通过使用新的Servlet 3.0 Futures(如Async-Support或asyncContext.addListener(asyncListener)或其他我不知道的东西)来改进此代码.由于我从未关闭流,我想知道我的服务器将如何扩展

从理论上讲,最好的方法是在新数据出现时通过服务器端代码显式触发doGet() - 方法,因此客户端不需要触发客户端"onmessage()" - 方法,因此服务器端"doGet()" - 每3秒对新数据进行一次方法.

Era*_*dan 13

这是一个很好的问题,这是一个完整的工作示例(Servlet 3.0/Java EE 6)

一些说明:

  1. 它通过out.checkError()调用来处理"浏览器选项卡/窗口关闭"flush()
  2. 我写的很快,所以我确信它可以改进,只是一个POC,在测试之前不要在生产中使用

Servlet :(为简洁省略了导入,很快就会更新完整的要点)

@WebServlet(urlPatterns = {"/mySSE"}, asyncSupported = true)
public class MyServletSSE extends HttpServlet {

  private final Queue<AsyncContext> ongoingRequests = new ConcurrentLinkedQueue<>();
  private ScheduledExecutorService service;

  @Override
  public void init(ServletConfig config) throws ServletException {
    final Runnable notifier = new Runnable() {
      @Override
      public void run() {
        final Iterator<AsyncContext> iterator = ongoingRequests.iterator();
        //not using for : in to allow removing items while iterating
        while (iterator.hasNext()) {
          AsyncContext ac = iterator.next();
          Random random = new Random();
          final ServletResponse res = ac.getResponse();
          PrintWriter out;
          try {
            out = res.getWriter();
            String next = "data: " + String.valueOf(random.nextInt(100) + 1) + "num of clients = " + ongoingRequests.size() + "\n\n";
            out.write(next);
            if (out.checkError()) { //checkError calls flush, and flush() does not throw IOException
              iterator.remove();
            }
          } catch (IOException ignored) {
            iterator.remove();
          }
        }
      }
    };
    service = Executors.newScheduledThreadPool(10);
    service.scheduleAtFixedRate(notifier, 1, 1, TimeUnit.SECONDS);
  }

  @Override
  public void doGet(HttpServletRequest req, HttpServletResponse res) {
    res.setContentType("text/event-stream");
    res.setCharacterEncoding("UTF-8");

    final AsyncContext ac = req.startAsync();
    ac.setTimeout(60 * 1000);
    ac.addListener(new AsyncListener() {
      @Override public void onComplete(AsyncEvent event) throws IOException {ongoingRequests.remove(ac);}
      @Override public void onTimeout(AsyncEvent event) throws IOException {ongoingRequests.remove(ac);}
      @Override public void onError(AsyncEvent event) throws IOException {ongoingRequests.remove(ac);}
      @Override public void onStartAsync(AsyncEvent event) throws IOException {}
    });
    ongoingRequests.add(ac);
  }
}
Run Code Online (Sandbox Code Playgroud)

JSP:

<%@page contentType="text/html" pageEncoding="UTF-8"%>
<!DOCTYPE html>
<html>
    <head>
        <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
        <title>JSP Page</title>
        <script>
            function test() {
                var source = new EventSource('mySSE');
                source.onopen = function(event) {
                    console.log("eventsource opened!");
                };

                source.onmessage = function(event) {
                    var data = event.data;
                    console.log(data);
                    document.getElementById('sse').innerHTML += event.data + "<br />";
                };
            }
            window.addEventListener("load", test);
        </script>
    </head>
    <body>
        <h1>Hello SSE!</h1>
        <div id="sse"></div>
    </body>
</html>
Run Code Online (Sandbox Code Playgroud)

  • 一个缓慢的客户端读取会减慢所有其他客户端的写入速度,因为这种技术使用阻塞写入。(这是 2013 年的适当答案)。现代应用程序可能应该使用带有异步 I/O 写入的 Servlet 3.1。 (2认同)
  • Joakim:这真的有问题吗?我刚刚做了一个试运行。两个客户端,一个在 alert() 中阻塞。服务器每 30 秒向两者写入一条短消息。一夜之间毫无障碍地跑了起来。也许链中有很多缓冲,但仍然...... (2认同)