db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DERBY-4702) Determine if the DRDA Layber B DSS extended total length field should carry a signed or unsigned integer
Date Tue, 21 Feb 2012 20:00:49 GMT

     [ https://issues.apache.org/jira/browse/DERBY-4702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Kathey Marsden updated DERBY-4702:
----------------------------------

    Urgency: Low
     Labels: derby_triage10_9  (was: )
    
> Determine if the DRDA Layber B DSS extended total length field should carry a signed
or unsigned integer
> --------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-4702
>                 URL: https://issues.apache.org/jira/browse/DERBY-4702
>             Project: Derby
>          Issue Type: Task
>          Components: Network Client, Network Server
>    Affects Versions: 10.7.1.1
>            Reporter: Kristian Waagan
>            Priority: Minor
>              Labels: derby_triage10_9
>
> The client and the server disagrees on whether the extended total length field in the
DRDA protocol is signed or unsigned.
> A search in the DRDA specification (version 4) was fruitless.
> I don't think the current situation results in any practical problems, but it would be
nice to determine what the correct representation is and to make the client and the server
consistent.
> This issue was brought up under DERBY-1595.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message