I am developing a Wap applikation were I present a list of items in the Wap-client. I have verified that the deck size is below the recommended size.
The problem is that after some updates (3-4) of the list I get some sort of error in the client and the same error occures if the deck is to large.
It seems that the client or maybee the Wap Gateway is buffering information in some way. I do not use the card attribute 'newcontext' since I do not want to loose the navigation history.
If 'newcontext' is not used, is the client buffering information in some way? If it is, does it take space from the "other" bytes?
Could the problem lie in the Wap Gateway?
I use the Wap Gateway of Telia in sweden but I do not know the type of the Wap Gateway.
Posted by Johan Berneskog, firstname.lastname@example.org
on August 29, 2000 at 19:04