Databases
StackOverflow2013
Postsdbo
POWebSockets served by a Servlet Container
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POWebSockets served by a Servlet Container
    primarykey
    data
    text
    <p>I was taking a look at WebSockets last week and made a few thoughts on how to implement the server side with the Java Servlet API. I didn't spend too much time, but ran into the following problems during a few tests with Tomcat, which seem impossible to solve without patching the container or at least making container specific modifications to the HttpServletResponse implementation:</p> <ul> <li><p>The WebSocket specification mandate a defined message in the 101 HTTP response. HttpServletResponse.setStatus(int code, String message) is deprecated without mentioning a usable replacement. After changing the default Tomcat configuration, I made Tomcat honor my message string, but since the method is deprecated, I'm not sure if this will work with other servlet containers.</p></li> <li><p>The WebSocket specification require a specified order of the first few headers in the HTTP response to the connection upgrade request. The servlet API does not offer a method to specify the order of the response headers and Tomcat adds its own headers to the response, placing a few of them before any headers, which are added by the servlet implementation.</p></li> <li><p>Since the content length of the response is not known when committing the header, Tomcat automatically switches to chunked transfer encoding for the response, which is incompatible with the WebSocket specification.</p></li> </ul> <p>Am I missing something obvious, or is it really not possible to integrate WebSocket server endpoints in a servlet based web app?</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USBalusC
    1. USjarnbjo
    plurals
    1. This table or related slice is empty.
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POWebSockets served by a Servlet Container
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POWebSockets served by a Servlet Container
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POWebSockets served by a Servlet Container
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI ran into pretty much the same issues. I really wanted to extend Tomcat, to show how I would like a "WebSocket Servlet" to look like, when its added to the Java EE specs. To see how I hacked Tomcat, you can look at the patches at http://java.dzone.com/articles/tomcat-websockets-html5
      singulars
      1. POWebSockets served by a Servlet Container
      1. USAnt Kutschera
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload