[
https://issues.apache.org/jira/browse/DERBY-6801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14642032#comment-14642032
]
Abhinav Gupta commented on DERBY-6801:
--------------------------------------
Hi Bryan,
I did go through the patch to ensure that things were in place but I didn't
notice that messageUtils wasn't added to the version control in my current
sandbox. I've attached the patch MessageUtils_latest.diff again with the latest
class. The constants are now only present in the MessageUtils class but they
are still public.
Thanks,
Abhinav.
> Implement MessageUtils class so client and server can share message argument
> encoding/decoding
> ----------------------------------------------------------------------------------------------
>
> Key: DERBY-6801
> URL: https://issues.apache.org/jira/browse/DERBY-6801
> Project: Derby
> Issue Type: Sub-task
> Components: JDBC, Network Client, Network Server
> Reporter: Bryan Pendleton
> Assignee: Abhinav Gupta
> Priority: Minor
> Attachments: MessageUtilsBryan.diff, MessageUtils_2.diff,
> MessageUtils_3.diff, MessageUtils_Latest.diff,
> MessageUtils_StandardEx_1.diff, MessageUtils_StandardExcep.diff, build.out,
> messageUtils.diff, messageUtils_1.diff, subPart2.diff, unsealDerbyNetJar.diff
>
>
> Currently, the Network Server contains code which encodes message arguments
> to be passed over DRDA to the client, and other code which
> decodes the encoded message arguments when the client passes
> them back in a call to SQLCAMESSAGE (see DERBY-1178 for additional
> discussion of this behavior).
> We would like to extract that logic and place it into a new MessageUtils
> class in the common shared library so that both the client and server
> can manipulate the message arguments without duplicating the code.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
