As far as I can tell, the advantage of one over the other would
depend on the kind of data being encoded. Base64 will always (I
think) increase the total size by about a third, whereas Urlencoding
will do better on text, but worse on binary data, I think. Other than
that, I don't know of any issues.
Best,
Mark
On 8 Jan 2009, at 10:05, David Bovill wrote:
2009/1/7 Mark Smith <[email protected]>
On reason that you might have had trouble base64encoding is that
it inserts
a newline every 80th (I think) byte, so you only need that to
happen once to
mess up a scheme that relies on line delimiters. In fact, you can
remove the
newlines that it inserts, and it doesn't seem to cause problems with
base64decode...
That's useful to know Mark - added to the scrap book. One thing I'd
like to
know is if there is any advantage to using base64encoding over url
encoding
for transmission over http? That is if you are rolling your own
protocol -
and so can choose what you implement.
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your
subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
