Kent Williams
Moderator
Username: Kent
Post Number: 123
Registered: 10-2003
| | Posted on Tuesday, May 17, 2005 - 06:18 pm: | |
Hi Marc,
This is an issue of real-world usability vs. strict adherence to the specification. And in this case, our customers have told us that they prefer real-world usability.
However, it is still possible to configure the proxy to strictly adhere to the SDU size limit. Simply edit WAPGW.INI, and under the [WAPGW] header, add ResponseSizeLimits=Yes.
In older versions of the proxy, we used to strictly adhere to these limits (the default setting was ResponseSizeLimits=Yes), but we spent too much support time telling people how to change this setting.
The issue is that most clients that claim a max SDU size of 300,000, can actually handle larger content. They arbitrarily picked a limit of 300,000 because of limitations of SAR (segmentation and re-assembly), which has a limit of 254 segments in basic SAR.
Prior to v2.55, we set our limit at 254*1400, or 355,600. That is why you would see a limit applied to a 357KB object.
However, in the current v2.55 version of Now.WAP, we'll actually transmit objects over 500KB, which most of these 300KB limit clients can handle. (We'll include a header in the first segment that tells the size, and the client can send an abort if it can't accept it.)
Technically, it is breaking the rules, but as Java games have gotten larger, we have quite a few customers that have been asking for this capability.
If you want to follow the rules, then edit WAPGW.INI, and under the [WAPGW] header, add ResponseSizeLimits=Yes.
-Kent |
Search
Last
