Skip to main content

[jsr356-experts] Re: Pings and Pongs

  • From: Greg Wilkins < >
  • To:
  • Subject: [jsr356-experts] Re: Pings and Pongs
  • Date: Fri, 13 Jul 2012 11:49:12 +1000

On 13 July 2012 11:10, Joe Walnes 
< >
 wrote:
>
> * Whatever the result of the streaming API discussion, we should offer
> equivalent methods for the ping/pong application date (e.g. chunking,
> streaming, whatever).

Pings and Pongs are control frames, so their payload size is limited
to 126 bytes.    I think a streaming API for this would be overkill
and prone to overflows.


> * Most (but not all) applications don't care about implementing their own
> ping/pong rules. It should be easy for applications to use predefined
> ping/pong strategies (e.g. reply to pings from client, send heartbeat pings
> from server with timeout, etc), without having to duplicate code.

+1






-- 
Greg Wilkins 
< >
www.webtide.com
Developer advice, services and support
from the Jetty & CometD experts.


[jsr356-experts] Pings and Pongs

Danny Coward 07/12/2012

[jsr356-experts] Re: Pings and Pongs

Joe Walnes 07/13/2012

[jsr356-experts] Re: Pings and Pongs

Greg Wilkins 07/13/2012

[jsr356-experts] Re: Pings and Pongs

Joe Walnes 07/13/2012

[jsr356-experts] Re: [jsr356-users] Pings and Pongs

Jitendra Kotamraju 07/13/2012
 
 
Close
loading
Please Confirm
Close