Table of Contents
Advertisement
Overview
This feature makes flexible way of preventing the large JAR files OTA download. The
current functionality is as follows:
•
In order to let the different operators utilize this feature there shall be ability to use flex
database element to limit the maximum size of the JAR file. The appropriate notice shall
be displayed to inform the user that the maximum JAR file size is exceeded and
downloading is rejected. The maximum JAR file size value shall come directly from a
customer requirement or product team.
There may be 2 types of MIDlets download:
•
•
This feature does not consider JAR-only download. The behavior in this case is specified
by "J2ME Download MIDlet Through Browser" feature.
•
•
•
•
Prevent Downloading of
Large Java MIDlets
The user is able to download any JAR file independently from its file size via the
WAP browser. In some cases the MIDlet can not be executed properly due to the
limited heap memory size of a Java enabled phone. In this case the user is
charged for the data transfer (not for the event) and in some cases this charge
will be higher than the cost of MIDlet itself.
JAR-only file download
JAR/JAD file download
The system shall support setting the maximum JAR file size for downloading.
This feature shall apply only to JAR accompanied by JAD files download.
The maximum JAR file size for the download shall be stored in the flex database.
The default size value shall be set to maximum available value for the flex
database element.
14
95
Advertisement
Table of Contents
