Dear sir, Thanks! In a word, now kannel doesn't support Complex Multipart (embedded multipart message MIME) sepecified in rfc2049.
Best Regards, Guanghua Hou ----- Original Message ----- From: "Stipe Tolj" <[EMAIL PROTECTED]> To: "Aarno Syvänen" <[EMAIL PROTECTED]> Cc: "ghhou" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Monday, November 17, 2003 5:50 PM Subject: Re: sub MIME in PAP > Aarno Syvänen wrote: > > > > PAP is mostly used to send SI, SLs and MMS notifications, so content is very > > specific here (and not the actual content). > > > > Aarno > > > > On 14.11.2003, at 09:32, ghhou wrote: > > > > Dear sir, > > > > Does kannel support multiple push contents in PAP interface? That is, in the second MIME entity of PAP data, the content -type is "multipart", and multiple push contents are contained in the sub-MIME. > > AFAIU, the question is, if PPG is able to receive multiparted body as > content to send multiple documents to a device without the need to > pass 2 or 3 PPG requests, correct? > > No, PPG is not able to handle multiparts in there. @Aarno, I think > this is right? > > But you can addopt things with gwlib/mime.[ch] functions to make PPG > support multipart content entities. Patches welcome ;) > > Stipe > > mailto:[EMAIL PROTECTED] > ------------------------------------------------------------------- > Wapme Systems AG > > Münsterstr. 248 > 40470 Düsseldorf, NRW, Germany > > phone: +49.211.74845.0 > fax: +49.211.74845.299 > > mailto:[EMAIL PROTECTED] > http://www.wapme-systems.de/ > ------------------------------------------------------------------- > > -----BEGIN PGP PUBLIC KEY BLOCK----- > Version: GnuPG v1.2.2 (Cygwin) > > mIsEP6mcYwEEAMDnUiUwrbb+xwTFWN6TxF2+XZu7/alwJMeCwMBRvXtPZqfjpPhS > OkBpU0F4TrVuugz1HINTSaJTYq10AzDQXp5NkyWgckqW79nPAWuOX0dicbJk+cN2 > nM2TI4KaxUDe6u8hghNEnH/i2lXsUu9apnP/iixzV81VC2je3uc9hZpnAAYptEVT > dGlwZSBUb2xqIChUZWNobm9sb2d5IENlbnRlciAmIFJlc2VhcmNoIExhYikgPHRv > bGpAd2FwbWUtc3lzdGVtcy5kZT6ItAQTAQIAHgUCP6mcYwIbAwYLCQgHAwIDFQID > AxYCAQIeAQIXgAAKCRABV0w1BqPYRuSqA/wPzsQxao2YePENCtgRTrO86U6zg3sl > OcS6CJFI4FZP5h/xD3GRsNH1+MPSvZlomDdpFnr547DGz/Kq9MXuQwVvlVig5yWZ > K5dtKp1r5YLhxJQBhfirZbRFFnYmf19f18J8OoS28tuFVftDl1AIwJS3HLyBTv6H > g2HyLAEKQIp30Q== > =aYCI > -----END PGP PUBLIC KEY BLOCK----- >