Return-Path: Delivered-To: apmail-incubator-harmony-dev-archive@www.apache.org Received: (qmail 73200 invoked from network); 26 Apr 2006 09:20:59 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 26 Apr 2006 09:20:58 -0000 Received: (qmail 80865 invoked by uid 500); 26 Apr 2006 09:20:41 -0000 Delivered-To: apmail-incubator-harmony-dev-archive@incubator.apache.org Received: (qmail 80810 invoked by uid 500); 26 Apr 2006 09:20:41 -0000 Mailing-List: contact harmony-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: harmony-dev@incubator.apache.org Delivered-To: mailing list harmony-dev@incubator.apache.org Received: (qmail 80789 invoked by uid 99); 26 Apr 2006 09:20:41 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 26 Apr 2006 02:20:40 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of zhanghuangzhu@gmail.com designates 66.249.82.200 as permitted sender) Received: from [66.249.82.200] (HELO xproxy.gmail.com) (66.249.82.200) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 26 Apr 2006 02:20:40 -0700 Received: by xproxy.gmail.com with SMTP id t16so974190wxc for ; Wed, 26 Apr 2006 02:20:19 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=KuAYEjkaW15FbQTCb1lAy6++E//frtVq2cCkVQCts33YLhHdxNQJXgCLsjh9VNWmtOAujSfOOzvssSA4pfRNUDwUEyidhKoFoFF3prEO/EgNPr26mqUfDt88kwU45WSwxyuFOvve+vGczvgmGOU5DJAStD8Wup784npg5sGp/8c= Received: by 10.70.105.7 with SMTP id d7mr323310wxc; Wed, 26 Apr 2006 02:20:19 -0700 (PDT) Received: by 10.70.124.1 with HTTP; Wed, 26 Apr 2006 02:20:19 -0700 (PDT) Message-ID: <4d0b24970604260220y5568920ar284eca95ff87423b@mail.gmail.com> Date: Wed, 26 Apr 2006 17:20:19 +0800 From: "Andrew Zhang" To: harmony-dev@incubator.apache.org Subject: Re: [jira] Commented: (HARMONY-410) method decode(ByteBuffer, CharBuffer, boolean) should set correct position in ByteBuffer In-Reply-To: <444F365D.2040804@gmail.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_9755_20398386.1146043219419" References: <444F365D.2040804@gmail.com> X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N ------=_Part_9755_20398386.1146043219419 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hi Vladimir, I think we both understand the spec :) Here I propose two solutions: 1. Set the ByteBuffer to the limit, and store the remaining ByteBuffer in decoder. Invokers doesn't care the position of in. If the result is UNDERFLOW and there're furthur input, just pass the new input to the decoder. It's a typical streaming decoder. That's what Harmony does currently. 2. Decoder doesn't store remaining ByteBuffer. Position of "in" is set to indicate the remaining ByteBuffer. Invoker should take care to generate new input ByteBuffer for next invocation. RI acts in this way. Both are acceptable. However, I think solution 1 is more reasonable. "Is it possible to store bytes in decoder, support streaming decoding, and, at the same time sets correct position in input buffer after each operation= ? " Yes. In fact, your patch will make Harmony act as the description above. However, I don't think it solve the problem. Maybe invoker is more confusable and may think: "Is the remaining bytebuffer maintained in decoder or in ? Shall I get the remaining buffer from in and pass it for next invocation?" Anyway, we need a decision on this compatibility issue. By the way, Vladimir, does solution one cause any problem on other classlib implementation? Any comment? Thanks ! Vladimir Strigun commented on HARMONY-410: ------------------------------------------ Hi Richard, Thanks for the clarification, I agree that streaming decode is good thing, but I'd like to explain my understanding of specification :) According to specification of CharsetDecoder decoding operation should process by the following steps: " 2. Invoke the decode method zero or more times, as long as additional input may be available, passing false for the endOfInput argument and filling the input buffer and flushing the output buffer between invocations; 3. Invoke the decode method one final time, passing true for the endOfInput argument; and then " spec also says: "The buffers' positions will be advanced to reflect the bytes read and the characters written, but their marks and limits will not be modified" I understand these sentences in the next way: invoke decode with endOfInput =3D false if you have additional input, then fill the buffer (i.e. add to buffer some additional input), invoke decode again and pass correct endOfInput parameter dependent of availability of input. Example you provided is very useful and, of course, 1st option looks better= , but what I'm suggest here is to reflect actual processed bytes in input. After first invocation of decode, not all bytes processed actually, i.e. almost all bytes processed, but some stored in decoder to further operation= . Is it possible to store bytes in decoder, support streaming decoding, and, at the same time sets correct position in input buffer after each operation= ? Thanks. Vladimir. > method decode(ByteBuffer, CharBuffer, boolean) should set correct positio= n in ByteBuffer > ---------------------------------------------------------------------------= ------------- > > Key: HARMONY-410 > URL: http://issues.apache.org/jira/browse/HARMONY-410 > Project: Harmony > Type: Bug > Components: Classlib > Reporter: Vladimir Strigun > Assignee: Mikhail Loenko > Priority: Minor > Attachments: Harmony-410_patch.txt, harmony-410_test.txt > > When ByteBuffer contain incomplete sequence of bytes for successful decoding, position in ByteBuffer should be set to latest successful byte. I will attach testcase and patch soon. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- Andrew Zhang China Software Development Lab, IBM ------=_Part_9755_20398386.1146043219419--