Open GoogleCodeExporter opened 9 years ago
We are providing base64 encoding/decoding now on both sides which are already
used for file transfer via web sockets until the binary transmission in the
next web socket draft has been specfified.
Original comment by fivefeetfurther@gmail.com
on 5 Aug 2010 at 9:22
[deleted comment]
One way i see to transfer binary data is to escape it so that it can be places
into a string element (i.e. zero or more Unicode chars in double quotes using
backslash escapes) in JSON. but when we escape by putting extra characters the
data size might increase.
http://en.wikipedia.org/wiki/Yenc this can be handy too to convert binary to
text.. haven't looked at in detail but looks good. also compression before
encoding (and after decoding) may be helpful..
Original comment by mailtopu...@gmail.com
on 11 Aug 2010 at 7:47
oh that's what we are already doing :)
Original comment by mailtopu...@gmail.com
on 11 Aug 2010 at 7:51
We have working base64 encoder. See FileSystemPlugin.
If we expected that the binary protocol release still takes times, we may
introduce a more compressing solution, but to me for now that seems to be
low-priority improvement. Let's wait a bit for the binary spec before further
actions.
Original comment by fivefeetfurther@gmail.com
on 9 Sep 2010 at 1:24
Original comment by fivefeetfurther@gmail.com
on 14 Oct 2010 at 2:26
Original issue reported on code.google.com by
fivefeetfurther@gmail.com
on 7 Jun 2010 at 1:28