> From: John Wilson [mailto:[EMAIL PROTECTED]] > the code ignores whitespace. > Which I take to mean that "=" or "==" should not be followed by non > whitespace characters. So I think I'm justified in flagging this as an > error. John -- You're right... :) I missed the bytes at the head of your translation table. But I also I grabbed the wrong snippet of code; this was the one that I wanted: + } else if (sixBit == 66) { + throw new Error("bad character \'" + c + "\' in base64 value"); This one should let the character go (p. 25): if (sixBit == 66) byteShift--; Cheers, Paul
- Re: Bas64 encoding performance Jon Scott Stevens
- Re: Bas64 encoding performance Rick Blair
- Re: Bas64 encoding performance John Wilson
- Re: Bas64 encoding performance John Wilson
- Re: Bas64 encoding performance John Wilson
- Re: Bas64 encoding performance John Wilson
- RE: Bas64 encoding performance Paul Brown
- Re: Bas64 encoding performance John Wilson
- Re: Bas64 encoding performance Jon Scott Stevens
- Re: Bas64 encoding performance John Wilson
- Re: Bas64 encoding performance Paul Brown
- Re: Bas64 encoding performance John Wilson
- Examples of XM-RPC servlets Christer Nordvik
- Proxy Authentication Paul
- Re: Proxy Authentication Daniel Rall
- Re: Bas64 encoding performance Daniel Rall
- Re: Bas64 encoding performance Jason van Zyl
- Re: Bas64 encoding performance Jon Scott Stevens
- Re: Bas64 encoding performance Hannes Wallnoefer
- Re: Bas64 encoding performance Rick Blair
- Re: Bas64 encoding performance John Wilson