otaspecification.html

J2ME MIDP2.0 final specification

	</th>
	<th rowspan="1" colspan="1">
	  <p class="TableHead">
	    Status Message</p>
	</th>
      </tr>
      <tr>
	<td rowspan="1" colspan="1">
	  <p class="TableText">
	    900</p>
	</td>
	<td rowspan="1" colspan="1">
	  <p class="TableText">
	    Success</p>
	</td>
      </tr>
      <tr>
	<td rowspan="1" colspan="1">
	  <p class="TableText">
	    901</p>
	</td>
	<td rowspan="1" colspan="1">
	  <p class="TableText">
	    Insufficient Memory</p>
	</td>
      </tr>
      <tr>
	<td rowspan="1" colspan="1">
	  <p class="TableText">
	    902</p>
	</td>
	<td rowspan="1" colspan="1">
	  <p class="TableText">
	    User Cancelled</p>
	</td>
      </tr>
      <tr>
	<td rowspan="1" colspan="1">
	  <p class="TableText">
	    903</p>
	</td>
	<td rowspan="1" colspan="1">
	  <p class="TableText">
	    Loss of Service</p>
	</td>
      </tr>
      <tr>
	<td rowspan="1" colspan="1">
	  <p class="TableText">
	    904</p>
	</td>
	<td rowspan="1" colspan="1">
	  <p class="TableText">
	    JAR size mismatch</p>
	</td>
      </tr>
      <tr>
	<td rowspan="1" colspan="1">
	  <p class="TableText">
	    905</p>
	</td>
	<td rowspan="1" colspan="1">
	  <p class="TableText">
	    Attribute Mismatch</p>
	</td>
      </tr>
      <tr>
	<td rowspan="1" colspan="1">
	  <p class="TableText">
	    906</p>
	</td>
	<td rowspan="1" colspan="1">
	  <p class="TableText">
	    Invalid Descriptor</p>
	</td>
      </tr>
      <tr>
	<td rowspan="1" colspan="1">
	  <p class="TableText">
	    907</p>
	</td>
	<td rowspan="1" colspan="1">
	  <p class="TableText">
	    Invalid JAR</p>
	</td>
      </tr>
      <tr>
	<td rowspan="1" colspan="1">
	  <p class="TableText">
	    908</p>
	</td>
	<td rowspan="1" colspan="1">
	  <p class="TableText">
	    Incompatible Configuration or Profile</p>
	</td>
      </tr>
      <tr>
	<td rowspan="1" colspan="1">
	  <p class="TableText">
	    909</p>
	</td>
	<td rowspan="1" colspan="1">
	  <p class="TableText">
	    Application authentication failure</p>
	</td>
      </tr>
      <tr>
	<td rowspan="1" colspan="1">
	  <p class="TableText">
	    910</p>
	</td>
	<td rowspan="1" colspan="1">
	  <p class="TableText">
	    Application authorization failure</p>
	</td>
      </tr>
      <tr>
	<td rowspan="1" colspan="1">
	  <p class="TableText">
	    911</p>
	</td>
	<td rowspan="1" colspan="1">
	  <p class="TableText">
	    Push registration failure</p>
	</td>
      </tr>
      <tr>
	<td rowspan="1" colspan="1">
	  <p class="TableText">
	    912</p>
	</td>
	<td rowspan="1" colspan="1">
	  <p class="TableText">
	    Deletion Notification</p>
	</td>
      </tr>
    </table>

    <a name="AdditionalAttributes"></a>
    <h2 class="SectionTitle">Additional Descriptor Attributes</h2>
      <p class="Paragraph">
	The following additional attributes are defined in the
	Application Descriptor. Each may appear only once in the
	descriptor.</p>
      <br><b>MIDlet Attributes</b>
      <table class="Table" border="1">
      <tr>
	<th rowspan="1" colspan="1">
	  <p class="TableHead">
	    Attribute Name </p>
	</th>
	<th rowspan="1" colspan="1">
	  <p class="TableHead">
	    Attribute Description</p>
	</th>
      </tr>
      <tr>
	<td rowspan="1" colspan="1">
	  <p class="TableText">
	    MIDlet-Install-Notify</p>
	</td>
	<td rowspan="1" colspan="1">
	  <p class="TableText">
	    The URL to which a POST request is sent to report the
	    installation status (whether a new installation or MIDlet
	    suite update) of this MIDlet suite. The device MUST use
	    this URL unmodified. The URL MUST be no longer than 256
	    UTF-8 encoded characters. If the device receives a URL
	    longer than 256 UTF-8 encoded characters it MUST reject
	    the installation and return <a href="#StatusCodes"><em
	    class="Code">Status Code 906</em></a> in the status
	    report.</p>
	</td>
      </tr>
      <tr>
	<td rowspan="1" colspan="1">
	  <p class="TableText">
	    MIDlet-Delete-Notify</p>
	</td>
	<td rowspan="1" colspan="1">
	  <p class="TableText">
	    The URL to which a POST request is sent to report the
	    deletion of this MIDlet suite. The device MUST use this
	    URL unmodified. The URL MUST be no longer than 256 UTF-8
	    encoded characters. If the device receives a URL longer
	    than 256 UTF-8 encoded characters it MUST reject the
	    installation and return <a href="#StatusCodes"><em
	    class="Code">Status Code 906</em></a> in the status
	    report.</p>
	</td>
      </tr>
      <tr>
	<td rowspan="1" colspan="1">
	  <p class="TableText">
	    MIDlet-Delete-Confirm</p>
	</td>
	<td rowspan="1" colspan="1">
	  <p class="TableText">
	    A text message to be provided to the user when prompted to
	    confirm deletion of this MIDlet suite</p>
	</td>
      </tr>
    </table>

    <a name="DevIdReqHdr"></a>
    <h2 class="SectionTitle">Device Identification and Request Headers</h2>
    <p class="Paragraph">
      The process of discovering a MIDlet suite via the DA can be
      customized by the device sending information about itself to the
      server. The DA MUST provide the network server with information
      (e.g. the manufacturer and device model number) so that the
      server can determine the device's capabilities. In many cases, a
      DA will already have identified the device type to the server by
      means consistent with its network connection and markup
      language.</p>
    <p class="Paragraph">
      During the download of a MIDlet suite, a device SHOULD identify
      its characteristics and the type of the content being requested
      as completely as possible to the server. The HTTP
      request-headers used to fetch the content MUST include, <em
      class="Code">User-Agent, Accept-Language</em>, and <em
      class="Code">Accept</em>. Servers SHOULD use this additional
      information to select the appropriate Application Descriptor for
      the device.</p>

    <h3 class="SectionTitle">User-Agent Product Tokens</h3>
    <p class="Paragraph">
      The MIDP specification identifies HTTP <em class="Code">
      User-Agent</em> request headers to identify the client to the
      server. RFC2616 specifies a format for product tokens such
      as:</p>
    <p class="Codeline">
      <em class="Code">"User-Agent" ":" 1*(product
      | comment)</em></p>
    <p class="Paragraph">
      The product tokens used to identify the device as supporting
      CLDC and MIDP are specified the <a
      href="javadoc/javax/microedition/io/package-summary.html#UserAgentHeaders">Networking</a>
      portion of the MIDP specification. As in RFC2616, the comment
      field is optional.</p>
    <p class="Paragraph">
      In addition, the device SHOULD further identify itself by adding
      a device-specific product token to the <em class="Code">
      User-Agent</em> header as defined by RFC2616. The
      device-identifying token SHOULD be the first token. The
      product-token and product-version values are specific to each
      device and are outside of the scope of this specification.</p>

    <h3 class="SectionTitle">Accept-Language Header</h3>
    <p class="Paragraph">
      The device MAY supply the <em class="Code">Accept-Language</em>
      request-header as specified in RFC2616 to indicate the language
      that is in use on the device.</p>

    <h3 class="SectionTitle">Accept Header</h3>
    <p class="Paragraph">
      The <em class="Code">Accept</em> HTTP header is used to indicate
      the type of content being requested. When requesting MIDlet
      suites, this header SHOULD include <em class="Code">
      application/java-archive</em>. For retrieving application
      descriptors, this header SHOULD include <em class="Code">
      text/vnd.sun.j2me.app-descriptor</em>.</p>

    <h3 class="SectionTitle">
      Example: HTTP Request for Application Descriptor</h3>
    <p class="Paragraph">
      When requesting the download of an Application Descriptor, the
      request headers might look as follows:</p>
    <p class="Codeline">
      GET http://host.foo.bar/app-dir/game.jad HTTP/1.1<br>
      Host: host.foo.bar<br>
      Accept: text/vnd.sun.j2me.app-descriptor<br>
      User-Agent: CoolPhone/1.4 Profile/MIDP-2.0 Configuration/CLDC-1.0<br>
      Accept-Language: en-US, fi, fr<br>
      Accept-Charset: utf-8</p>
    <p class="Paragraph">
      The response headers from the server might look as follows:</p>
    <p class="Codeline">
      HTTP/1.1 200 OK<br>
      Server: CoolServer/1.3.12<br>
      Content-Length: 2345<br>
      Content-Type: text/vnd.sun.j2me.app-descriptor; charset=utf-8</p>