activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Hiram Chirino <hi...@hiramchirino.com>
Subject Re: Apollo usage of heart-beat header in Stomp 1.0 CONNECTED frame
Date Mon, 25 Jun 2012 13:54:44 GMT
Hi Michael,

Please refer to the heart beating section of the STOMP 1.1 spec for more
details [1].

In short, since a STOMP 1.0 connection does send the 'heart-beat' header,
it's the same as if the client would have sent a 'heart-beat:0,0' which
means ti does not want any heart beats from the sever, and it can't send
any heart beats to the server.  So no, it does really change
the behavior of STOMP 1.0 clients.


[1]: http://stomp.github.com/stomp-specification-1.1.html#Heart-beating

On Sun, Jun 24, 2012 at 9:25 AM, Michael Justin <michael.justin@gmx.net>wrote:

> Hello,
>
> I noticed that Apollo 1.3 include a heart-beat header in CONNECTED frames
> with value 100,10000
>
> This value seems to be constant, even if the client uses Stomp 1.0. Does
> this header mean that in Stomp 1.0 mode
>
> * the broker will send a heart-beat signal every 100 milliseconds
> * the broker expects a message (or a heart-beat signal) from the client
> every 10000 milliseconds
>
> or does this header have no actual meaning in Stomp 1.0 mode?
>
> Example:
>
> CONNECT
> login:admin
> passcode:password
> accept-version:1.0
> server:localhost
>
> CONNECTED
> version:1.0
> server:apache-apollo/1.3
> session:mybroker-7da
> heart-beat:100,10000
> user-id:admin
>
> Regards
>
> --
> Michael Justin
> habarisoft - Enterprise Messaging Software for Delphi
> http://www.habarisoft.com/
>
>


-- 

**

*Hiram Chirino*

*Software Fellow | FuseSource Corp.*

*chirino@fusesource.com | fusesource.com*

*skype: hiramchirino | twitter: @hiramchirino<http://twitter.com/hiramchirino>
*

*blog: Hiram Chirino's Bit Mojo <http://hiramchirino.com/blog/>*

*
*

*
*

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message