Re: [PATCH] Siemens SX1 kludge

You are rigth, I give up.
I have printed basic rules from one of the first final WSP spec (1998).
As I see it was changed. Heh, I'll need to refresh some printed hand-on
materials :(.

Aarno Syvänen wrote:
> Slave, what spec are you reading ?
> 
>  From WAP-203-WSP-20000504, clause 8.4.2.1:
> 
> Constrained-encoding = Extension-Media | Short-integer
> ; This encoding is used for token values, which have no well-known 
> binary encoding, or when
> ; the assigned number of the well-known encoding is small enough to fit 
> into Short-integer.
> 
> Extension-media = *TEXT End-of-string
> ; This encoding is used for media values, which have no well-known 
> binary encoding
> 
> Aarno
> 
> On 21.1.2005, at 10:11, Vjacheslav Chekushin wrote:
> 
> 
> 
>     Stipe Tolj wrote:
> 
>         Vjacheslav Chekushin wrote:
> 
>             Just remark.
> 
>             SX1 behavior _NOT_ conforms to wap specification, because
>             besides general
>             encoding there is well-known encoding for Accept header:
> 
>             8.4.2.7 Accept field
>             The following rules are used to encode accept values.
>             Accept-value = Constrained-media | Accept-general-form
>             Accept-general-form = Value-length Media-range
>             [Accept-parameters]
>             Media-range = (Well-known-media | Extension-Media) *(Parameter)
>             Accept-parameters = Q-token Q-value *(Accept-extension)
>             Accept-extension = Parameter
>             Constrained-media = Constrained-encoding
>             Well-known-media = Integer-value
>             ; Both are encoded using values from Content Type
>             Assignments table in Assigned Numbers
>             Q-token = <Octet 128> )
> 
>             And we have: Accept-general-form => Value-length Media-range
>             [Accept-parameters]
> 
>             So value-length is 0 and Media-range (mandatory) is absent.
> 
>             So Accept header must be either as string "Accept: ..." or
>             "80 ..."
>             and in the last case it _MUST_ be encoded as Accept-value.
> 
>         ok, agreeing for the 'Accept-value = Constrained-media |
>         _Accept-general-form_' value. _BUT_ what about _Constrained-media_?
>         If comes up to Extension-media where the reference BNF is used.
>         IMO the Accept encoded byte 0x80 followed by a 0*TEXT (hence
>         nothing), followed by a end-of-string 0x00 is allowed then.
>         Comments on this please.
> 
> 
>     My comments:
> 
>     Constrained-media = Constrained-encoding
>     Constrained-encoding = Token-Text | Short-Integer
>     Token-Text = Token End-of-string
>     Token = 1*<any CHAR except CTLs or tspecials> (from RFC 2068)
> 
>     So, we _need_ at least 1 non End-of-string simbols ;)
> 

>     Vjacheslav Chekushin mailto:[email protected]
>     Latvian Mobile Phone Company http://www.lmt.lv
> 
> 
> 
> 


-- 
Vjacheslav Chekushin                                mailto:[email protected]
Latvian Mobile Phone Company                        http://www.lmt.lv