db-torque-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Greg Monroe" <Greg.Mon...@DukeCE.com>
Subject Base64 support question
Date Wed, 14 Jun 2006 20:42:04 GMT
I've got the ColumnValueUtil class (which originally was called
ColumnValueConverter) 
pretty much done and am starting to do the TestCase for it.  However,
there is one
issue I'd like input from others on... Base64 encoding support.
 
If you remember from the e-mails about this feature, this class will
help convert between
Column Object values to Strings and vice versa.  In order to support
String representations
of  Binary types of data (e.g. BLOB, Binary, VarBinary, etc), I am using
Base64 encoding.
My current code uses the Base64 class in the commons-codex library to do
this.  
 
However, it seems like a lot of work and problems to add yet another
library to the
Torque runtime, just for one class that impliments a very stable and
fully understood
encryption method.
 
Should this library be added?  
 
Or can we "borrow" (with full accrediation) the Base64 class from
commons-codex and 
re-packages just this class into a torque package?
 
Thoughts, cries of outrage, proper process for this, or what ever.
 
TIA.
 
Greg
Greg Monroe <Monroe@DukeCE.com> (919)680-5050
C&IS Solutions Team Lead
Duke Corporate Education, Inc.
333 Liggett St.
Durham, NC 27701


 

Duke CE Privacy Statement
Please be advised that this e-mail and any files transmitted with it are confidential communication
or may otherwise be privileged or confidential and are intended solely for the individual
or entity to whom they are addressed.  If you are not the intended recipient you may not rely
on the contents of this email or any attachments, and we ask that you  please not read, copy
or retransmit this communication, but reply to the sender and destroy the email, its contents,
and all copies thereof immediately.  Any unauthorized dissemination, distribution or copying
of this communication is strictly prohibited.



Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message