MWS:Phone Software

From OpenSource

Options

Note that all options are not available simultaneously.

Start w. Connector

Starts Apache and the connector. That is, when started like this, your mobile phone becomes visible on the web.

Start w/o Connector

Starts Apache. Choose this if you only want to browse to the webserver locally using the browser on your phone or over Bluetooth, USB or WLAN.

Start Connector

Starts the connector.

Stop Connector

Stops the connector without stopping Apache.

Restart Webserver

Restarts Apache. Note that this means restarting according to Apache parlance. That is, Apache is not stopped and started, but the httpd.conf file is re-read and evaluated.

Settings

Invokes the settings dialog.

Properties

Invokes the properties dialog where the On Portal and Mobsite hopping properties can be set.

• On portal specifies whether or not your mobsite is visible on a portal when you are online. NOTE The portal is currently disabled, so the setting carries no meaning.
• Mobsite hopping specifies whether your mobsite can be found from another mobsite that is whether your mobsite is implicitly linked by other mobsites in the proximity of yours.

Out of site

Invokes a dialog where the out-of-site messages can be set. The out-of-site message is shown by the gateway when someone tries to browse to your mobsite and you are offline.

License

Shows the license of the software.

Notice

Shows attribution notices.

Exit

If the setting Stop on Exit is Yes stops Apache and the connector and exits the application. If the setting is No exits the application but leaves Apache and the connector running in the background.

Stop and Exit

Stops Apache and the connector and exits the application.

Settings

Identifier & Password

These are used for identifying your terminal and thus allows the gateway to map a particular URL to a specific terminal. Note that these have nothing to do with access control of people browsing to your mobsite.

Access Point

The access point to be used when connecting to the gateway.

Stop on Exit

If this setting is Yes then when exiting the UI, Apache and the connector are stopped as well. If it is No, then when exiting the UI, Apache and the connector are not stopped but left running in the background.

NOTE There is no visual clue that would tell you whether Apache and the connector are running in the background or not.

Gateway

The IP address of the gateway.

Gateway port

The port used in the communication between the terminal and the gateway.

Max Connections

There is a, so called, control connection maintained between the terminal and the gateway at all times. In addition, there is one, so called, data connection for each concurrent HTTP request intended for the mobsite. This setting defines the maximum number of concurrent data connections and a value of 0 specifies that there is no upper limit. If a limit specified and it is reached, then the gateway will serialize the requests as needed. Idle data connections are reused and they don't stay around forever but are cleaned up when they go stale (see Keepalive Interval below).

Keepalive interval

A TCP/IP connection in a cellular network does not remain alive forever, but goes stale after a while unless there is traffic going over it. In practice this means that there must be, so called, keepalive traffic, from the gateway to the terminal, when there is no "natural" traffic. This setting specifies how many seconds apart, the gateway should send a keepalive message to the terminal. A value of 0 means that the interval is dynamically probed and adjusted as needed, depending on the current network characteristics. Fixing the interval at too high a value makes your mobsite unreachable for some part of the time and fixing it at a very low value drains your battery.

Keepalive max latency

This setting specifies the additional time - in addition to the keepalive interval - that the terminal waits for a keepalive message before it assumes that the control connection has gone stale. This should be bigger than 0 as there will always be some latency but not much as that means it takes longer than necessary before it is detected that the connection has gone stale. 10 seconds should be fine for most contexts. Note that this value is ignored if the keepalive interval is 0. In that case also the latency is dynamically adjusted.

Reconnect Interval

If the connection is broken and cannot be re-established immediately, this settings specifies how many seconds the terminal should wait between connection attempts.

Server

The IP address of the webserver. When running on the terminal this is in practice always 127.0.0.1, that is, localhost, but when developing and running under the emulator it may occasionally be useful to be able to use another IP address.

Server port

The IP port of the webserver.

Portal

The IP address of the portal server that is contacted when setting, for instance, the out-of-site message. If it is all zeros, then the IP address is assumed to be the same as that of the gateway.

Portal port

The IP port of the portal server.