I tried an SSE (Server-Sent-Events) using java on tomcat 8.0. Here are few things I noticed.

I click a button that automatically makes a request to the servlet. Servlet's GET method gets executed which returns an event stream. Once the full stream is received, the page again automatically makes another request which receives the same data again!!! I don't have an infinite loop there!!!

1. What is actually happening on the server? In normal scenarios, tomcat creates a thread to handle every request. What is happening now?
2. What is the correct way to ensure that the event stream is sent only once to the same connection/browser session?
3. What is the correct way to ensure that the event stream is closed and no resource overhead incurs on the server?
4. How to differentiate between GET and POST requests. Why did it choose GET?
5. Is it too early to use SSE on Tomcat? Any performance issues?

Here is the code for the curious,

```
@WebServlet("/TestServlet")
public class TestServlet extends HttpServlet {

    public void doGet(HttpServletRequest request, HttpServletResponse response)
            throws ServletException, IOException {

        //content type must be set to text/event-stream
        response.setContentType("text/event-stream"); 
        //cache must be set to no-cache
        response.setHeader("Cache-Control", "no-cache");     
        //encoding is set to UTF-8
        response.setCharacterEncoding("UTF-8");

        PrintWriter writer = response.getWriter();

        for(int i=0; i<10; i++) {
            System.out.println(i);
            writer.write("data: "+ i +"\n\n");
            writer.flush();
            try {
                Thread.sleep(3000);
            } catch (InterruptedException e) {
                e.printStackTrace();
            }
        }
        writer.close(); 
    }
}

```

Javascript on the page (I don't have anything else on the page),

```
<button onclick="start()">Start</button>

<script type="text/javascript">
    function start() {
        var eventSource = new EventSource("TestServlet");
        eventSource.onmessage = function(event) {
            console.log("data: "+event.data)
            document.getElementById('foo').innerHTML = event.data;
        };
    }
</script>

```

Tried this using CURL. And the response came just once. I'm using chrome, so this must be a issue with chorme??

**EDIT:**

What I have learned and learning is now documented in my blog - [Server Sent Events](http://www.cs-repository.info/2016/08/server-sent-events.html)
['https://Stackoverflow.com/questions/31768349', 'https://Stackoverflow.com', 'https://Stackoverflow.com/users/548634/']
I highly recommend first to read [Stream Updates with Server-Sent Events](http://www.html5rocks.com/en/tutorials/eventsource/basics/) to get a good general understanding of the technology.
Then follow [Server-Sent Events with Async Servlet By Example](https://weblogs.java.net/blog/swchan2/archive/2014/05/21/server-sent-events-async-servlet-example) to see how SSE can be used specifically with the Servlet technology.
The browser attempts to reconnect to the source roughly 3 seconds after each connection is closed. You can change that timeout by including a line beginning with "retry:", followed by the number of milliseconds to wait before trying to reconnect.