Re: Re[2]: Siemens S55 WAP problems fixed?! PATCH

Hi Jury & Stipe

I am -1 this, too. Minimal patch is to remove *all* 1.4 version headers.
(Then Kannel would support 1.3)

But untokenized Content-Types should indeed work. 1.4 means only
that the phone will accept tokenised headers, too.

Aarno

On Saturday, April 19, 2003, at 10:33 PM, Jury Cherepanov wrote:

> Hello Stipe,
>
> Saturday, April 19, 2003, 8:03:30 PM, you wrote:
>
> ST> -1 for this patch. This is the "too easy" solution and breaks our 
> new
> ST> MMS encoder/decoder routines that are based on WSP parsing code.
>
> ST> Beware that Nokia and Ericsson *do* use the tokenized form in their
> ST> WSP headers, so we have to take care to be able to read them.
>
> ST> Stipe
>
> ST> [email protected]
> ST> -------------------------------------------------------------------
> ST> Wapme Systems AG
>
> ST> Vogelsanger Weg 80
> ST> 40470 Düsseldorf
>
> ST> Tel: +49-211-74845-0
> ST> Fax: +49-211-74845-299
>
> ST> E-Mail: [email protected]
> ST> Internet: http://www.wapme-systems.de
> ST> -------------------------------------------------------------------
> ST> wapme.net - wherever you are
>
> So seems that i'm wrong :)
> But.
> Nokia and ericcson phones convert header encoded content types to
> internal string values like tokenized => string.
> It also works in this direction string => string.
> And seems no matter what is coming from WAP gate, tokenized or string
> value. Basicaly that must be encoded according WAP specification.
>
> Also, if it breaks your MMS encoder/decoder that your encoder/decoder
> is "too easy" solution.
>
> When you send notification message to phone throught SMS you can
> encode it with tokenized or string value, both phone understands
> correctly (Nokia, Siemens, Ericsson).
>
>
> ---------------------------------------------------------
> Jury Cherepanov
> System Developer (Technical Director) , HIGH TECHNOLOGIES
> Turaidas 2a, Riga, Latvia
> Phone +371-9633398
> mailto:[email protected]
>
>
>