Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <14420209.1151666672036.JavaMail.jira@brutus>
Date: Fri, 30 Jun 2006 11:24:32 +0000 (GMT+00:00)
From: "Tomohito Nakayama (JIRA)" <derby-dev@db.apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Resolved: (DERBY-1461) Separate writeScalarStream to methods
 which handle either encrypted or plain streams.
In-Reply-To: <24570975.1151506710351.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

     [ http://issues.apache.org/jira/browse/DERBY-1461?page=all ]
     
Tomohito Nakayama resolved DERBY-1461:
--------------------------------------

    Resolution: Fixed

Committed.

Sending        java/client/org/apache/derby/client/net/Request.java
Transmitting file data .
Committed revision 418240.

> Separate writeScalarStream to methods which handle either encrypted or plain streams.
> -------------------------------------------------------------------------------------
>
>          Key: DERBY-1461
>          URL: http://issues.apache.org/jira/browse/DERBY-1461
>      Project: Derby
>         Type: Sub-task

>     Reporter: Tomohito Nakayama
>     Assignee: Tomohito Nakayama
>  Attachments: DERBY-1461.patch
>
> Reading writeScalarStream in Request class,
>  I found it would be possible to separate this method to two methods,
> one is for encrypted stream and another is for plain,
> because original writeScalarStream hardly share code for encrypted and for plain.
> Separating this method will help me to realize DERBY-1301 separatingly for encrypted and plain,
> as I planned in http://issues.apache.org/jira/browse/DERBY-1301#action_12417684 .

-- 
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