Member Function Documentation

This involves consulting a list of unsafe ports, corresponding to network services that may be easily exploitable. If the given port is considered unsafe, then the protocol handler (corresponding to aScheme) will be asked whether it wishes to override the IO service's decision to block the port. This gives the protocol handler ultimate control over its own security policy while ensuring reasonable, default protection.

While this is set, IOService will monitor an nsINetworkLinkService (if available) and set its offline status to "true" whenever isLinkUp is false.

Applications that want to control changes to the IOService's offline status should set this to false, watch for network:link-status-changed broadcasts, and change nsIIOService::offline as they see fit. Note that this means during application startup, IOService may be offline if there is no link, until application code runs and can turn off this management.

When in offline mode, attempts to access the network will fail (although this is not necessarily corrolated with whether there is actually a network available -- that's hard to detect without causing the dialer to come up).