Jetty

User should have chance to turn on KEEP_ALIVE option for a socket (especially for continuation)

Details

  • Type: Improvement Improvement
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Won't Fix
  • Affects Version/s: 6.1.10
  • Fix Version/s: None
  • Component/s: Bayeux, Continuations
  • Labels:
    None
  • Environment:
    linux 2.6.24-17-generic #1 SMP i686 GNU/Linux
  • Number of attachments :
    0

Description

Currently the users have no chance to turn on the KEEP-ALIVE option for the sockets created by jetty in configuration files. But it is really important, especially for continuation:

For example, a use made a long polling, and waiting on a continuation. Then user plugged the network cable out of the computer, shutdown the computer, and went home. In the jetty side, we never know the user has left without a KEEP-ALIVE socket connection, and continuation is be in jetty forever until jetty restart.

A similar issue is: http://jira.codehaus.org/browse/JETTY-593 . But in 593, the process of web browser will send a FIN to jetty server. But in this case, nothing will be send to notify the jetty server.

Activity

Hide
Permalink
Greg Wilkins added a comment -

Jetty uses persistent connections by default for HTTP/1.1 and if requested by the client for HTTP/1.0.

To notice if a user has left, you need to set a maxInterval timeout and implement a RemoveListener so you are called back when the client is gone.

you can see the demo bayeux webapp for examples of this.

Show
Greg Wilkins added a comment - Jetty uses persistent connections by default for HTTP/1.1 and if requested by the client for HTTP/1.0. To notice if a user has left, you need to set a maxInterval timeout and implement a RemoveListener so you are called back when the client is gone. you can see the demo bayeux webapp for examples of this.

People

  • Assignee:
    Unassigned
    Reporter:
    Temp
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: