Re: AW: Kannel PPG, PI and character encoding

Hi Jörg, Jörg Pommnitz wrote: Code for BASE64 encoded Push content is now in CVS. Please have a look. It looks nice, and it will be easy to add new encodings. Aarno

Re: AW: Kannel PPG, PI and character encoding

Hi Jörg, Code for BASE64 encoded Push content is now in CVS. Please have a look. What do you do with Content-Encoding header ? If you change encoding, you must change the header, too. Aarno

AW: AW: Kannel PPG, PI and character encoding

What do you do with Content-Encoding header ? If you change encoding, you must change the header, too. Aarno Good question. It should be changed to binary, shouldn't it? Regards Jörg

Re: AW: Kannel PPG, PI and character encoding

Hi Jörg, Jörg Pommnitz wrote: I just read RFC2387: it uses base64 as transfer encoding for application/octet-stream data. While there is a void octstr_base64_to_binary(Octstr *ostr) function in the Kannel source tree it seems not to be used in the PPG code. Aarno, what's your opinion?

Re: AW: AW: Kannel PPG, PI and character encoding

]] Gesendet am: Dienstag, 23. Oktober 2001 11:50 An: Jörg Pommnitz Cc: [EMAIL PROTECTED] Betreff: Re: AW: Kannel PPG, PI and character encoding Hi Jörg, Jörg Pommnitz wrote: I just read RFC2387: it uses base64 as transfer encoding for application/octet-stream data. While

AW: Kannel PPG, PI and character encoding

I just read RFC2387: it uses base64 as transfer encoding for application/octet-stream data. While there is a void octstr_base64_to_binary(Octstr *ostr) function in the Kannel source tree it seems not to be used in the PPG code. Aarno, what's your opinion? Regards Jörg -Ursprüngliche