RE: WML deck size limitation...

Hi Seishi and all.

The maximum SDU size of WSP depends on the bearer MTU size and what kind of 
WTP protocol options (e.g. SAR: Segmentation and Re-assembly) are supported.
WSP defines the default value, which is 1400 octets for both client and WAP 
gateway. But it is negotiable.

Assuming that the bearer MTU size is 1500 octets and no WTP options are 
used. The maximum SDU size of WSP is
1500 - '(IP)/WDP(UDP)/WTP header size'

If the MTU size of bearer is larger, a client can handle larger data. It 
might be a good idea to check the bearer MTU size first.

Best Regards,
Hidetoshi Ueno

At 09:23 01/04/03 +0900, Seishi TSUKADA wrote:

>Hi Tomas and all
>
>Thank you for quick follow up and available information.
>Based on my understanding, the limitation of WTP payload has
>limitation as 1500KB. When WAP gateway and terminal support
>SAR (Segmentation and Re-assembly), they can send more
>data in one packet. But SAR is an optional function, so some
>terminal may not support this (e.g. NOKIA 7110).
>
>Best Regards.
>Seisi Tsukada
>
>At 08:25 01/04/02 +0200, Tomas.Majak@speedytomato.net wrote:
>>Hi,
>>
>>To my understandings, there is no limitation in decksize in WSP, rather it
>>is a li,itation in the terminal memory. Nokia 7110 has "kind of" setted the
>>standard here with it's limitation of not being able to handle wmlc
>>files(compiled version of wml) larger than 1400 bytes. How ever there are
>>several terminals that can handle more than that Ericsson R320, which can
>>handle 2400 bytes (not 100% sure about exact size). The problem with the
>>compliation of WML is that it just compiles the tags, no attributes or
>>PCDATA. One way to shorten the length of a deck is to put parts of
>>frequently occurring links in a variable named 'x', thus you just have to
>>write that part of the url once....
>>
>>Hope that i made my self clear
>>
>>Regards
>>Tomas Majak
>>
>>-----Original Message-----
>>From: Seishi TSUKADA [mailto:tsukada@mmd.yrp.nttdocomo.co.jp]
>>Sent: den 30 mars 2001 09:56
>>To: Ashwini Tambi; www-mobile@w3c.org
>>Subject: Re: WML deck size limitation...
>>
>>
>>Hi Ashwini
>>
>>My understand is the limitation of packet size comes from
>>the WAP protocol, WSP (Wireless Session Protocol).
>>The default value of WSP packet size is 1400 byte, which
>>include WML contents and WSP header.
>>WAP Gateway encodes a WML file and sends the encoded file
>>to the WAP terminal, so the size of WML text file (before encoded)
>>may be larger than 1400 byte.
>>
>>Best Reards
>>Seishi Tsukada
>>
>>At 21:34 01/03/29 -0800, Ashwini Tambi wrote:
>> >Hi,
>> >
>> >I am a beginner in WML programming world and currently
>> >I am porting one PC-based website for mobile phones.
>> >
>> >The existing website contains ASP pages with HTML
>> >which I have transformed into WML. I have tested the
>> >website using Nokia WAP toolkit 2.0 emulator and it
>> >works fine. However, when I test the same website
>> >using the actual Nokia 7110 cellphone, it does not
>> >work properly all throughout. While browsing the site,
>> >the initial 3 decks are shown properly but when I
>> >attempt to go to the next deck by clicking next
>> >button, it says "connection time out" after a while.
>> >
>> >I found that the size of the .wmlc file for this deck
>> >is ~2k. Is this the only problem ? The size limitation
>> >sounds to be a very common problem. One apparent
>> >solution is to redesign the website and sub-divide one
>> >deck into multiple decks to limit the size of .wmlc
>> >file below 1400 bytes. However, it is not readily
>> >acceptable in my case. Any other solution ?
>> >
>> >Is there any other aspect of the problem I am
>> >overlooking ?
>> >
>> >Looking forward to your expert suggestions.
>> >
>> >Thanks with regards,
>> >Ashwini
>> >
>> >__________________________________________________
>> >Do You Yahoo!?
>> >Get email at your own domain with Yahoo! Mail.
>> >http://personal.mail.yahoo.com/?.refer=text
>

Received on Tuesday, 3 April 2001 01:51:41 UTC