Re: Base64 encoding on Leopard
Re: Base64 encoding on Leopard
- Subject: Re: Base64 encoding on Leopard
- From: Stephen Hoffman <email@hidden>
- Date: Wed, 21 Nov 2007 11:51:58 -0500
- Organization: HoffmanLabs LLC
Here's some of what a Base64 search in Xcode documentation search turns up:
http://developer.apple.com/samplecode/QTSSConnectionMonitor/listing4.html
http://developer.apple.com/samplecode/QTSSInspector/listing3.html
Apache license. Full source.
Using and embedding source code can be feasible and expedient, but there
have been cases where a common source code module (conversion or
otherwise) turned out to be buggy, and a pile of folks ended up having
to rebuild their respective applications with the corrected source
code. In some cases, these operations can have security implications.
Most anything involving user-generated or user-provided data processing
can be (is) a target.
Having an embedded conversion library would certainly be useful; whether
in CF or CD or otherwise. There are various other formats where
conversions could be useful. URL encoding, EBCDIC, Unicode, accented
Romance text to unaccented text, ROT13, etc. (Ok, ROT13 was a joke.)
There are ways to perform these data conversions scattered around, but
AFAICT there's no central document nor central reference for these
existing conversion operations. And no conversion library.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Macnetworkprog mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden