db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (JIRA)" <derby-...@db.apache.org>
Subject [jira] Created: (DERBY-951) Change network client code to be more clear that it only supports Network Server's encoding for Fdoca data
Date Fri, 10 Feb 2006 22:52:05 GMT
Change network client code to be more clear that it only supports Network Server's encoding
for Fdoca data
----------------------------------------------------------------------------------------------------------

         Key: DERBY-951
         URL: http://issues.apache.org/jira/browse/DERBY-951
     Project: Derby
        Type: Improvement
  Components: Network Client  
    Versions: 10.2.0.0    
    Reporter: Kathey Marsden
    Priority: Minor
     Fix For: 10.2.0.0


The network client code is unclear and inconsistent in the way it passes around ccsid and
encodings.  This improvement will change the client code to make it clear that it only supports
UTF-8 for FD:OCA  data as sent by Network Server.
See discussiion at:
http://www.nabble.com/Client-decoding-of-server-Fdoca-data%2C-which-direction-do-we-want-to-go--t1096517.html#a2869822

That discussion suggests adding the static encoding value to Configuration.java but I think
perhaps Typedef.java is a better place.  Also need to investigate proper error handling on
the client side if server sends a different CCSID. Should we reject with a proper error or
just ignore the CCSID and assume it is 1208.






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


Mime
View raw message