Return-Path: Delivered-To: apmail-activemq-users-archive@www.apache.org Received: (qmail 79859 invoked from network); 21 Sep 2007 10:14:11 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 21 Sep 2007 10:14:11 -0000 Received: (qmail 48233 invoked by uid 500); 21 Sep 2007 10:14:01 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 48198 invoked by uid 500); 21 Sep 2007 10:14:01 -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 48189 invoked by uid 99); 21 Sep 2007 10:14:01 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 21 Sep 2007 03:14:01 -0700 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of nathan.mittler@gmail.com designates 209.85.198.188 as permitted sender) Received: from [209.85.198.188] (HELO rv-out-0910.google.com) (209.85.198.188) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 21 Sep 2007 10:13:59 +0000 Received: by rv-out-0910.google.com with SMTP id l15so630962rvb for ; Fri, 21 Sep 2007 03:13:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; bh=0jt+HRFAm/xkpQ2tnC7l2NUx2MdsEq2fSkh6oymoxtc=; b=po+wJuzSIGfmQHqovEa8HEujoYX/Nb6uIAaHNUzUe/fRWCPRW+aFyF9AejVZEpTPif9S8W6VtFCU42BH4sB8V5+Y94i1DIdAy8/X+sulOi1/CpSPlRjHvAipPDbkt4FRupU2dkKIlH1MY+wRQ2jD9QQHPM5a9hzoiB1gOb0vsjU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=qN9VkMPUCjy/HpfpU9EOZyctMsENewLqZ6Fe/wd9yBTIZwfJIkjaZ7yq5gAMOvbgdDI2wveJTmglFIredBFC95w+N5wxOWYqCb1Bx6qN5R5TZXKPwcoCYbXNLaYQv+u50pmv9pW6/ozY0nRpvfm4DMpRaVfbmaSwEBhins+g7qA= Received: by 10.114.198.1 with SMTP id v1mr3326015waf.1190369618208; Fri, 21 Sep 2007 03:13:38 -0700 (PDT) Received: by 10.114.234.14 with HTTP; Fri, 21 Sep 2007 03:13:38 -0700 (PDT) Message-ID: <8a6feb940709210313l21848e68ma988567e0898328c@mail.gmail.com> Date: Fri, 21 Sep 2007 06:13:38 -0400 From: "Nathan Mittler" To: users@activemq.apache.org Subject: Re: BytesMessage constness In-Reply-To: <12813490.post@talk.nabble.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_37302_10289739.1190369618203" References: <12813490.post@talk.nabble.com> X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_37302_10289739.1190369618203 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline I agree, this definitely would be a pain since the onMessage method gives you a const Message. Could you capture this issue in JIRA? http://issues.apache.org/activemq/browse/AMQCPP Thanks, Nate On 9/21/07, Motl wrote: > > > Hi, > I once asked you why readBytes() and other read methods aren't const: > > http://www.nabble.com/BytesMessage-methods-tf3833767s2354.html#a10853672 > > But if only the stream pointer is updated, I suppose we could have another > solution here, i.e. > declare inputStream field as 'mutable': > > mutable io::ByteArrayInputStream inputStream; > > In that case we could keep read methods const. > > I am requesting for that because at the moment such non-const API forces > app > level either always deal with non-const objects or make > const_cast(), that's not good. > > -- > View this message in context: > http://www.nabble.com/BytesMessage-constness-tf4492790s2354.html#a12813490 > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > > ------=_Part_37302_10289739.1190369618203--