×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
The algorithm for base64 is documented in RFC2045 in section 6...
specifically, 6.8 I'm not exactly sure what you're asking here. You say
that you don't want anyone to write it for you. Okay, so what DO you
want?
I explained the algorithm somewhat in the article entitled "RPG and the
IFS: Text Files in the World" which was published in the January issue of
iSeries NEWS. Here's a link to that article on-line (requires a
ProVIP membership to the iSeries Network):
http://www.iseriesnetwork.com/article.cfm?id=19626
That article also contains a sample of encoding (but not decoding) base64
code.
There's also an RPG sample of base64 encoding (again, not decoding) in the
ENCODER4 module of HTTPAPI.
http://www.scottklement.com/httpapi/
Over the past 10 years or so, I've written five different implementations
of base64, and 3 of them were for the iSeries. So, if you have any
specific questions about the programming part of it, please ask.
But, aside from actually posting my decoding routine (which you
specifically say you don't want) I don't know how I can help you further?
On Wed, 23 Feb 2005 MWalter@xxxxxxxxxxxxxxx wrote:
I've been searching all day for a method or algorythm to decode base64
input streams. I've read the RFC1341 documentation. I've looked at C and
Java code. I'd like to keep it in RPG if at all possible. I'm not asking
anyone to write it for me, but, please point me in the right direction. I'm
really lost here.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.