Return-Path: X-Original-To: apmail-activemq-users-archive@www.apache.org Delivered-To: apmail-activemq-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id BB30B9938 for ; Mon, 25 Jun 2012 13:55:12 +0000 (UTC) Received: (qmail 21600 invoked by uid 500); 25 Jun 2012 13:55:11 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 21523 invoked by uid 500); 25 Jun 2012 13:55:11 -0000 Mailing-List: contact users-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@activemq.apache.org Delivered-To: mailing list users@activemq.apache.org Received: (qmail 21506 invoked by uid 99); 25 Jun 2012 13:55:11 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 25 Jun 2012 13:55:11 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of chirino@gmail.com designates 209.85.216.49 as permitted sender) Received: from [209.85.216.49] (HELO mail-qa0-f49.google.com) (209.85.216.49) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 25 Jun 2012 13:55:05 +0000 Received: by qabj40 with SMTP id j40so1444180qab.15 for ; Mon, 25 Jun 2012 06:54:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=+j+TtdX40MOEuBjRlpwIJc2iHtEeTMm7hknQPpYCD2Q=; b=l0L3ykcxo2q3+ZJQe05T7Z/Cxik6+Uu9jk7kQQn3Wnf3fODXTa5PVFZKeY7he1xAR2 PIHUlit6cl015j2KwzgXGsQNzk+UllzALTq+SvKXQ3h6VnK+ZSdJGNXmr70MIGOwnw5b vIkWCM3vcJLeZEsoF/vLN1EGjh/aP7+40jMA6VKWT0gMKJ0zG21W5m9qRWMdcXtPwNru LhxXIDJOuApYl2DCT7NFRS19Ymtb7JJQZ+xDjJTZWjlxnAk8vuZQ/ZN9yHcJVcqWUjyY 0TiTv4mUKTNxELOnlv8xyUiRgPt0nyWbgMSqYunH0Ut27U38BWq3eFw9IcpyEG/p43f2 9utg== MIME-Version: 1.0 Received: by 10.224.187.11 with SMTP id cu11mr20560260qab.24.1340632484915; Mon, 25 Jun 2012 06:54:44 -0700 (PDT) Sender: chirino@gmail.com Received: by 10.229.30.144 with HTTP; Mon, 25 Jun 2012 06:54:44 -0700 (PDT) In-Reply-To: <4FE71538.4030601@gmx.net> References: <4FE71538.4030601@gmx.net> Date: Mon, 25 Jun 2012 09:54:44 -0400 X-Google-Sender-Auth: cgl3qY5q03OvrpyrlDyE5JjvxwQ Message-ID: Subject: Re: Apollo usage of heart-beat header in Stomp 1.0 CONNECTED frame From: Hiram Chirino To: users@activemq.apache.org Content-Type: multipart/alternative; boundary=485b397dd68709a8ca04c34c53e7 X-Virus-Checked: Checked by ClamAV on apache.org --485b397dd68709a8ca04c34c53e7 Content-Type: text/plain; charset=ISO-8859-1 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 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 * *blog: Hiram Chirino's Bit Mojo * * * * * --485b397dd68709a8ca04c34c53e7--