Array-like object containing WebServerConnection objects representing the current connections to this Web server.

Connections remain in this collection even if they are closed. They are removed when there are no longer any references to the connection elsewhere in the system.

The name of the service, for example as defined in the widgetname element in the config.xml of a Opera Unite application.

The path of the service, for example as defined in the servicePath element in the config.xml of an Opera Unite application. In contrast to the serviceName, this name can only contain characters that are valid in an IRI.

The path includes a leading and trailing slash.

This way a service called "My Cool File Sharing (tm) (c)" can be identified as simply "share" in it's URL, i.e. http://work.john.operaunite.com/share.

In the example above this property would contain '/share/'.

Note that anything after the first path component is handled by the service.

You may run Web servers on different devices. The hostname contains the device name, username and proxy address, for example work.john.operaunite.com as in http://work.john.operaunite.com/wiki.

Note that this will always be a host name which contains the proxy name.

This property will not contain the 'admin.' subdomain, if it is used.

This property can be used to make a download link to the service and can also function as part of an auto update scheme.

Listening for requests is done by registering event listeners on the Web server. The "event name" corresponds to the path fragment of the URL after the service name, e.g. 'add' as in http://work.john.operaunite.com/wiki/add.

Registered event handlers are called with an event of the type WebServerRequestEvent.

Any request names starting with underscore ('_') is reserved and cannot be used.

The exceptions are the following request names, which have special meanings:

_index

Event fired when a user accesses the root of the service (i.e. http://work.john.operaunite.com/wiki). Use this to supply a default start page or similar for your service.

_request

Event fired when a user accesses any URL under the service. Use this to catch all requests to the server in a general fashion. You'll need to use the WebServerRequest.uri to distinguish the actual request URI. Listening for this event will also catch the _index request, but not _close.

_close

Event fired when a connection is closed. In this case the connection property of the event object is null.

Events for specific event listeners and _index events are fired before the _request event is fired. Consider the following code example:

opera.io.webserver.addEventListener('_request', generalhandler, false);
opera.io.webserver.addEventListener('add', addhandler, false);

The handlers for a specific path, including _index is called before _request.

If the user visits the URL http://work.john.operaunite.com/wiki/add, a WebServerRequestEvent is fired, and the addhandler is called, before the generalhandler method is called. This happens regardless of which event listener was registered first.

Shares a File from a mountpoint that has been acquired earlier, and makes it available under the path specified in the second argument.

The File can be a regular file, a directory or an archive.

The share is automatically deleted when the application is closed.

Example: If you have resolved a File to a given folder and then specify opera.io.webserver.shareFile(myFile, 'share'), it will be shared as the URL http://device.user.proxy/service/share

The path must be a valid URL path token, and should be a relative sub path of the service. It should not start with '../' or '/', but you may specify additional path tokens, like 'media/gfx/logo.png'.

The File can be a regular file, a directory or an archive, but it must be referenced by a mount point.

ALREADY_SHARED_ERR will be thrown if something is already shared on the given path The share is automatically deleted when the application is closed.

Note that if you have added a _request event handler, you will need to compare the incoming requests with the paths you have shared to see if the request matches a shared file. If so, you will need to call WebServerResponse.closeAndRedispatch() without changing the uri fo the request to send the request back to the Web server. On the second pass, the Web server will serve the shared file directly.

Example: In order to share a resolved File on the path 'media/gfx', you would do the following:

opera.io.webserver.sharePath('media/gfx', myFile);

The file will now be shared as the URL http://device.user.proxy/service/media/gfx.

When a file has been shared using sharePath(), it can be unshared again by calling this method with the same path used to share the file.

Example: Assume that a file has been shared on the path 'media/gfx', i.e. on the URL http://device.user.proxy/service/media/gfx/, calling this method as follows will unshare the file:

opera.io.webserver.unsharePath('media/gfx');