|
|
 | | Known Issues |
-
BinBucket does currently not do any checking for availability/version
before instantiating the ADODB.Stream and Msxml2.DomDocument
objects. This will lead to automation errors in case of one or more
aren't present on the client system.
-
When using the method [BinBucket].toBase64, you might need to adjust
the line wrapping depending on what you want to do with the data.
BinBucket just delivers the encoded chunk as-is from the Msxml document.
-
You cannot not currently pass in base64/hex encoded data directly into
a BinBucket. You'll need to decode them first. Having problems decoding
a Base64 encoded string, I suggest you check out the class
"Soya.Encode.Base64" for a pure javascript encoder/decoder.
-
Typecasting string->bytearray is very slow due to the fact
ADODB.Recordset converts the string to 32-bit values, rendering every
other byte a 0x00. These has to be manually weeded out after the
conversation has been completed. Currently this is taken care of with
a regexp /([\da-f]{2})00/g, so be aware of poor performance when
dealing with string to bytearray conversions. I welcome suggestions how
to improve the current solution. Maybe this is settable somehow at
the Recordset level...
| | | | |
|
Copyright(c) 2001-2005 Saltstorm.
All rights reserved.