Motorola E680 Technical Manual - Page 17

The User-agent String, User_agent String

Page 17 highlights

4 Downloading Applications The following error codes are supported: ƒ 900 Success ƒ 901 Insufficient Memory ƒ 902 User Cancelled ƒ 903 Loss Of Service ƒ 904 JAR Size Mismatch ƒ 905 Attribute Mismatch ƒ 906 Invalid Descriptor ƒ 907 Invalid JAR ƒ 908 Incompatible Configuration or Profile ƒ 909 Application Authentication Failure ƒ 910 Application Authorization Failure ƒ 911 Push Registration Failure ƒ 912 Deletion Notification ƒ 913 Required package not supported by device ƒ 999 Other errors Please be aware that the method used by the handset, as per the specifications, is POST. Using a GET (URL encoding) style for the URL will fail. This is not the correct use of the MIDlets JAD parameters. Possible Screen Messages Seen With Downloading: ƒ If JAR -file size does not match with specified size, it will display a dialog stating "Installation failed. Package invalid." To dismiss this dialog, press "OK". ƒ When downloading is done, the handset displays a transient notice "Download Completed" and starts to install the application. ƒ Upon completing installation, the handset displays a dialog "Install complete". To dismiss this dialog, press "OK". ƒ If the MANIFEST file is wrong, the handset displays a dialog stating "Installation failed. Package invalid." To dismiss this dialog, press "OK". ƒ If JAD does not contain mandatory attributes, "Installation failed. Package invalid." notice appears. The USER-AGENT String The following table describes USER_AGENT strings associated with Motorola devices: Motorola Device USER_AGENT STRING E680 User-Agent: MOT-E680/xx.xx.xx MIB/2.2 Profile/MIDP-2.0 Configuration/CLDC-1.1 The USER_AGENT string can be used to identify a handset and render specific content to it based on it information provided in this string (example CGI on a content server). These strings can be found in the connection logs at the content server. 17

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107

4
Downloading Applications
17
The following error codes are supported:
900 Success
901 Insufficient Memory
902 User Cancelled
903 Loss Of Service
904 JAR Size Mismatch
905 Attribute Mismatch
906 Invalid Descriptor
907 Invalid JAR
908 Incompatible Configuration or Profile
909 Application Authentication Failure
910 Application Authorization Failure
911 Push Registration Failure
912
Deletion Notification
913 Required package not supported by device
999 Other errors
Please be aware that the method used by the handset, as per the specifications, is POST.
Using a GET (URL encoding) style for the URL will fail. This is not the correct use of the
MIDlets JAD parameters.
Possible Screen Messages Seen With Downloading:
If JAR -file size does not match with specified size, it will display a dialog stating
“Installation failed. Package invalid.” To dismiss this dialog, press “OK”.
When downloading is done, the handset displays a transient notice “Download
Completed” and starts to install the application.
Upon completing installation, the handset displays a dialog “Install complete”. To
dismiss this dialog, press “OK”.
If the MANIFEST file is wrong, the handset displays a dialog stating “Installation
failed. Package invalid.” To dismiss this dialog, press “OK”.
If JAD does not contain mandatory attributes, “Installation failed. Package
invalid.” notice appears.
The USER-AGENT String
The following table describes USER_AGENT strings associated with Motorola devices:
Motorola Device
USER_AGENT STRING
E680
User-Agent: MOT-E680/xx.xx.xx MIB/2.2 Profile/MIDP-2.0
Configuration/CLDC-1.1
The USER_AGENT string can be used to identify a handset and render specific content to
it based on it information provided in this string (example CGI on a content server). These
strings can be found in the connection logs at the content server.