Closed Bug 21835 Opened 25 years ago Closed 25 years ago

need to add offline attribute to nsIIOService

Categories

(Core :: Networking, defect, P3)

All
Windows NT
defect

Tracking

()

VERIFIED FIXED

People

(Reporter: warrensomebody, Assigned: warrensomebody)

References

Details

We need to add an attribute to nsIIOService to say whether the browser is
offline or not. The socket transport will check this before trying to do any
network activity. The front-end will set this when it thinks it's going
offline.

It would be nice to try and detect whether the network is actually unavailable,
but we don't know how to do that without causing the dialup dialog to come up
(on Windows).
Status: NEW → ASSIGNED
Target Milestone: M14
I don't think it matters for this whether the network is available.  If I
explicitly choose to go offline I don't want you to use the network even if it's
there.  Detection of a connection is really only useful for the UI and shouldn't
affect the offline feature otherwise.

In other words, it would be nice to have a "network available" indicator in the
UI, but it wouldn't also be the online/offline control.

In addition, the concept of network available is somewhat loose since the OS
will transparently make it available in most circumstances.  The indicator
should really track whether a dialup connection already exists or isn't needed
because some other transport is available.

The code to detect an existing dialup connection is available in our local
sources, but not checked in because the overall feature didn't make the beta
cut.  If you're interested in using it please let me know.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
I added an offline attribute to IOService some time ago. Now it needs to be
hooked up to the UI.
Blocks: 24102
verif. - development related
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.