Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Date: Fri, 29 Apr 2011 10:54:03 +0000 (UTC)
From: "Knut Anders Hatlen (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: 
 <2007691169.11431.1304074443134.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Created] (DERBY-5210) Use java.nio.ByteBuffer in
 client.net.Request
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Use java.nio.ByteBuffer in client.net.Request
---------------------------------------------

                 Key: DERBY-5210
                 URL: https://issues.apache.org/jira/browse/DERBY-5210
             Project: Derby
          Issue Type: Improvement
          Components: Network Client
    Affects Versions: 10.9.0.0
            Reporter: Knut Anders Hatlen
            Assignee: Knut Anders Hatlen


We should see if we could use a java.nio.ByteBuffer instead of a byte array in org.apache.derby.client.net.Request, similar to what we did for DDMWriter in DERBY-2936. ByteBuffer provides some helper methods that allows us to simplify the code that puts multi-byte values into the buffer (like ByteBuffer.putShort(), putInt(), putLong()). It may also be a first step on the way to using a CharsetEncoder to encode strings without going via an intermediate throw-away byte array (see DERBY-5068 for details).

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira