Closed Bug 168186 Opened 23 years ago Closed 16 years ago

"max_cached_connections" pref doesn't stick

Categories

(MailNews Core :: Networking, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: bugzilla, Unassigned)

References

()

Details

if you set the "max_cached_connections" pref to 1 the pref gets reset to 2 the next time your start mozilla mail. I manually changed the pref in prefs.js so that I had: user_pref("mail.server.server1.max_cached_connections", 1); I then started mozilla and exited mozilla. No I had: user_pref("mail.server.server1.max_cached_connections", 2); the setting of the pref dont seem to stick. is this on purpose? and why? 20020911
setting it to 1 via the UI (Server Settings -> Advanced) doesn't work either. Perhaps we should alert people trying to set it to 1 if that's invalid. Accepting user input and then changing it is bad...:)
QA Contact: huang → gchan
else if (maxConnections < 2) { // forced to use at least 2 maxConnections = 2; rv = SetMaximumConnectionsNumber(maxConnections); } perhaps this should be reflected in the UI? Should we just make into a dropdown box with 2 - 5
Product: MailNews → Core
IMAP issue, cc'ing Emre.
Assignee: mscott → nobody
QA Contact: grylchan → mailnews.networking
Product: Core → MailNews Core
FIXED by bienvenu 2004-03-09 17:00 to at least 1 connection.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.