Details
-
Type:
Improvement
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 1.3.1
-
Fix Version/s: 1.4.11
-
Component/s: None
-
Labels:None
Description
The built-in Base64 encoder/decoder of XStream is not very fast. We were using it, but we just switched to the migbase64 (http://migbase64.sourceforge.net/) one. Tests show that this one is about 10 times as fast (on a Base64 string of 270000 length). Might be good to use that one instead. The project just exposes the java code, so the idea is (I think) that you copy the code into your own project, since it is only 1 file.
Activity
Hi Joerg,
We are using Xpp3 indeed. I have not had any issues with it so far. The encoded data in my case is indeed on 1 line.
regards,
Wim
Show
Wim Deblauwe
added a comment - Hi Joerg,
We are using Xpp3 indeed. I have not had any issues with it so far. The encoded data in my case is indeed on 1 line.
regards,
Wim
Wim Deblauwe
added a comment - Hi Joerg,
We are using Xpp3 indeed. I have not had any issues with it so far. The encoded data in my case is indeed on 1 line.
regards,
Wim 
Hi Wim,
how do you use it? It seems that you have to put the encoded data into one big line in the XML. When using line breaks, you have a specification mismatch, because the RFC used as basis for migbase64 implementation requires CRLF as end-of-line sequence, while the XML spec requires a conforming XML parser to drop the CR character of a end-of-line CRLF sequence silently. Xpp3 is non-conforming and you may succeed with decoding, but I expect decoding errors using a StAX parser...