AW: mmsbox

I think MMS will require a working SAR implementation. MMS messages
can easily exceed 64KB. So, some work on the WAP side of things will
be necessary.

Regards
  Joerg

-----Ursprüngliche Nachricht-----
Von: Stipe Tolj [mailto:[email protected]]
Gesendet: Donnerstag, 15. Juli 2004 15:24
An: Søren Hansen
Cc: [email protected]
Betreff: Re: mmsbox


Søren Hansen schrieb:
> 
> ons, 2004-07-14 kl. 14:08 skrev Søren Hansen:
> > *: I'm very keen on doing this, but as I work as a programmer for at
> > company that develops and hosts mobile solutions, I should ask my boss
> > for permission to develop this mmsbox for Kannel.
> 
> Well, what do you know? He took the time to respond to my e-mail so I've
> got my permission now, so I'm about to start coding, so you all better
> start preparing to answer a lot of stupid questions from me sometime
> soon. :-D
> 
> Here's the first one:
> The MMS encapsulation spec defines the binary encoding of a lot of the
> MMS headers. Should I just throw those into wap/wsp_strings.def or
> should I create a new file just for the MMS specifics?

nop! do a gateway/mms directory and use mms_encap_strings.def for
those. Try to be molularic as much as possible and leave the wap/ code
untouched.


Stipe

mailto:[email protected]
-------------------------------------------------------------------
Wapme Systems AG

Vogelsanger Weg 80
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-----