XP timebomb code needed for betas

VERIFIED FIXED

Status

Core Graveyard
Viewer App
P1
enhancement
VERIFIED FIXED
20 years ago
5 years ago

People

(Reporter: Chris Yeh, Assigned: rpotts (gone))

Tracking

Trunk
All
Windows NT

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

20 years ago
Something else you probably haven't thought of is timebomb code.

At some magical point, you'll be releasing betas, and you'll need a way to
disable the engine after a particular date and time, or relative to the first
launching of Raptor.

This should be implemented in an XP way.

Updated

20 years ago
Assignee: kipp → scullin

Updated

20 years ago
Assignee: scullin → valeski
(Reporter)

Updated

20 years ago
Priority: P2 → P1
(Reporter)

Comment 1

20 years ago
upping the priority on this now that all of 5.0 is based on raptor.

Updated

20 years ago
Assignee: valeski → rpotts
(Assignee)

Updated

20 years ago
Status: NEW → RESOLVED
Last Resolved: 20 years ago
Resolution: --- → FIXED
(Assignee)

Comment 2

20 years ago
OK... I've checked in some timebomb code into
mozilla/network/module/nsNetservice.cpp which is modelled after the old
"classic" timebomb code.

Once, persistant preferences are working, the timebomb code can switch over to a
preference rather than compiling the time into the code...

Updated

20 years ago
Status: RESOLVED → VERIFIED

Comment 3

20 years ago
Verified that, yes, there was an XP timebomb in the beta release. ;)
Product: Core → Core Graveyard

Updated

5 years ago
Blocks: 891020

Updated

5 years ago
No longer blocks: 891020
You need to log in before you can comment on or make changes to this bug.