WebView-HTTP Sample Pages
This directory contains sample web pages which may be customized if you like.
You need to modify them according to your settings or network environments
when you wish to provide your own web pages.
1. Creating web pages with applets
Web pages with applets contains the <applet> tag as follows:
<applet codebase="http://[HTTP_SERVER]/-wvdoc-01-/[APPLET_TYPE]/"
code="[APPLET_TYPE].class" archive="[APPLET_TYPE].zip"
...>
<param name=cabbase value="[APPLET_TYPE].cab">
<param name=url value="http://[HTTP_SERVER]/">
...
</applet>
(1) [HTTP_SERVER]
Replace [HTTP_SERVER] with the URI of the HTTP server. The URI of the HTTP
server is the combination of HTTP host and HTTP port: e.g. 192.168.100.1:80
provided that the IP address is 192.168.100.1 and the HTTP port is 80.
- HTTP host can be represented either with a host name or with an IP address.
If you specify a host name as HTTP host, make sure the name is registered
to some appropriate name server (e.g. DNS) and can be resolved by clients.
If you specify an IP address as HTTP host, automatic address translation
from <_I_P_A_D_D_R_> is useful and recommended rather than specifying the
actual IP address directly. By specifying the IP address as <_I_P_A_D_D_R_>,
you don't have to modify web pages when you change the IP address, and you
can also avoid address resolution problems when you use ethernet and ppp at
the same time.
- HTTP port is the port number which you have specified for the HTTP server.
If you use the standard port number 80 (the factory setting), you can omit
the HTTP port part in [HTTP_SERVER], otherwise you MUST always specify this
part appropriately.
(2) [APPLET_TYPE]
Replace [APPLET_TYPE] with the name of applets. Three types of applets are
provided: Glimpse, LiveApplet and SnapAnimator. Common parameters to them are
described below. Refer to the manual about applet specific parameters which
can be used to customize the behavior of applets.
- The codebase attribute indicates the location in which the applet archive
file is stored. Specify this attribute like:
Glimpse codebase="http://[HTTP_SERVER]/-wvdoc-01-/Glimpse/"
LiveApplet codebase="http://[HTTP_SERVER]/-wvdoc-01-/LiveApplet/"
SnapAnimator codebase="http://[HTTP_SERVER]/-wvdoc-01-/SnapAnimator/"
- The code attribute indicates the class name used to initialize the applet.
Specify this attribute like:
Glimpse code="Glimpse.class"
LiveApplet code="LiveApplet.class"
SnapAnimator code="SnapAnimator.class"
- The archive attribute indicates the ZIP format applet archive file. Specify
this attribute like:
Glimpse archive="Glimpse.zip"
LiveApplet archive="LiveApplet.zip"
SnapAnimator archive="SnapAnimator.zip"
- The cabbase parameter indicates the CAB format applet archive file. Specify
this parameter as the value attribute of param tag with name=cabbase like:
Glimpse value="Glimpse.cab"
LiveApplet value="LiveApplet.cab"
SnapAnimator value="SnapAnimator.cab"
- The url parameter indicates the HTTP server to which the applet accesses.
Specify this parameter as the value attribute of param tag with name=url
like value="http://[HTTP_SERVER]/" for Glimpse and LiveApplet. SnapAnimator
doesn't require the url parameter.
2. The behavior of applets and possible problems
When you open the web page which contains applet tags, the applet specified
with codebase and code attributes is downloaded to the browser. The Netscape
uses ZIP-file specified with the archive attribute and the Internet Explorer
uses CAB-file specified with the cabbase parameter. Archive files are stored
in the /archive directory in the internal file system as follows.
GLIMPSE.CAB Glimpse.zip
GLIMPSE.ZIP Glimpse.cab
LVAPPLET.CAB LiveApplet.zip
LVAPPLET.ZIP LiveApplet.cab
SNAPANIM.CAB SnapAnimator.zip
SNAPANIM.ZIP SnapAnimator.cab
IMAGEMAP.GIF Bitmaps used by LiveApplet
DIGITS.GIF Bitmaps used by SnapAnimator
The applet cannot be downloaded unless these files are stored in the /archive
directory. If you happen to remove these files, restore files by copying from
the enclosed CD-ROM by using ftp.
When the applet archive file is downloaded successfully, the applet specified
with the code attribute starts running. As the applet accesses to proprietary
URIs prefixed with the URI of the HTTP server specified with the url parameter,
applets cannot keep running if something is wrong with this value. In addition,
[HTTP_SERVER] in the codebase attribute and in the url parameter must be same
for security reasons.
3. Other notes
(1) Character set and applet tags
Sample web pages that contain applet tags have the following tag in the header.
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
It is recommended to add this tag into the header part because old versions of
Netscape (prior to 3.0) cannot extract parameter values without this tag. If
you wish to describe the page
(2) More about [HTTP_SERVER]
One major problem occurs by the mispatch between [HTTP_SERVER] in the web page
and the URI of the web page itself. Hostnames may commonly be used for URIs of
web pages which are added to the book marker of the browser or are embedded in
other web pages as links. On the other hand, using the IP address is generally
recommended for [HTTP_SERVER], and the IP address is automatically used if you
are using <_I_P_A_D_D_R_> notation. For accesses via proxies or via firewalls,
applets would not be displayed correctly when you use the hostname and the IP
address together.
Such situations arise from proxy settings of web browsers. Some proxy settings
may work correctly for hostnames but incorrectly for IP addresses. If you use
your camera server as a public site in the Internet, specifying the hostname to
[HTTP_SERVER] may possibly be the better solution.
Similar situation occur for networks with NATs. Particularly, it is a peculiar
example anyway, [HTTP_SERVER] must be either a hostname or an IP address which
corresponds to the global address when accessing the camera server in the local
address space from browsers in global address space. <_I_P_A_D_D_R_> convention
cannot be used in this case because it is translated not to the global address
but to the local address.
Download Driver Pack
After your driver has been downloaded, follow these simple steps to install it.
Expand the archive file (if the download file is in zip or rar format).
If the expanded file has an .exe extension, double click it and follow the installation instructions.
Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.
Find the device and model you want to update in the device list.
Double-click on it to open the Properties dialog box.
From the Properties dialog box, select the Driver tab.
Click the Update Driver button, then follow the instructions.
Very important: You must reboot your system to ensure that any driver updates have taken effect.
For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.