Uniform Resource Identifier (URI) is an application-level protocol used to obtain resources on the Internet. The S60 Browser handles URI schemes on a Nokia device by:
Fetching content over the network for the http:
and https: schemes.
Fetching content from the device (locally) for the file:
scheme.
Dispatching other schemes to the appropriate applications for handling.
See the table at the end of this section for a list of supported schemes.
Following are a few examples of how you can use a URI scheme in your website to enhance your visitors experience.
sms: The sms: scheme opens the SMS editor on the device. One popular use case allows visitors of your website to share interesting news with a friend. For example, a "Share this article with a friend" link at the end of an article. The following code illustrates adding a link that when selected, launches the SMS editor and places a link to the article (www.mywebsite.com/article/101010101.html) in the message body. The illustration that follows shows the link in the SMS editor when the link is selected.
<a href="sms:?body=http://www.mywebsite.com/article/101010101.html">Share this article with a friend</a>
wtai: The wtai: scheme executes the telephony function on the device. One popular uses case allows visitors to make a phone call directly from a Web page, for example to place an order for an item on the page. Another use case is for visitors to add a contact number to their phonebook directly from a Web page. The following code illustrates these use cases.
<a href="wtai://wp/mc;[phonnumber]">Call to order</a>
<a href="wtai://wp/ap;[phonenumber];[name]">Add us to your phonebook</a>
The table below summarizes the list of URIs supported by the S60 Browser and how it handles them.
URI scheme | Handled by the S60 Browser |
---|---|
HTTP | Browser fetches the content over the network using a standard HTTP connection, unless an unexpired copy of the content exists in cache. |
HTTPS | Browser fetches the content over the network using a secure HTTPS connection (i.e. using SSL/TLS). HTTPS content is not cached for security reasons. |
FILE | Browser fetches the content from the local file system. The S60 file system follows a logical drive lettering convention. |
WTAI | WTAI handler executes the telephony function specified in the URI. |
TEL | Telephony-related scheme from iMode standards. Handled similarly to WTAI above. |
CTI | Telephony-related scheme from iMode standards. Handled similarly to WTAI above. |
MAILTO | The platform’s messaging editor (Email in most cases) is opened with supported parameters filled in, if specified in the URI. |
RTSP | The content is fetched and handled by the default multimedia player on the platform. |
MMS | The content is fetched and handled by the default multimedia player on the platform. |
SMS | The SMS editor is opened with supported parameters filled in, if specified in the URLI. |
MMSTO | The MMS editor is opened with supported parameters filled in, if specified in the URLI. |
LocalApp | Specific native applications can be opened using this scheme and appropriate parameters. Supported applications include: Calendar, Messaging, and Phonebook. |
Any other scheme not listed above | Browser dispatches the URI to a platform scheme dispatcher. If any application has registered for that scheme, it will receive it for handling. Otherwise an error will be shown to the user. |