Closed Bug 2918 Opened 26 years ago Closed 16 years ago

nsnotify: mail notification client uses short IMAP sessions

Categories

(MailNews Core :: Networking, defect, P2)

All
Solaris
defect

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: jgmyers, Unassigned)

Details

(Whiteboard: [Perf] nsnotify's future is unclear)

(This bug imported from BugSplat, Netscape's internal bugsystem. It was known there as bug #334286 http://scopus.netscape.com/bugsplat/show_bug.cgi?id=334286 Imported into Bugzilla on 02/04/99 16:49) The mail notification client sets up and tears down an IMAP connection every poll interval. This leads to poor server performance, as connection setup is expensive.
I think it's somewhat unlikely that nsnotify will be enhanced much in 5.0, but I'll leave it open just in case.
QA Contact: 4104
I think nsnotify relies a bit on Communicator so we might need to either make 5.0 do the things that 4.x did for nsnotify, or change nsnotify. I don't remember the exact details, but the winfe was setting IMAP uid highwater marks and things in a way that nsnotify knew how to look for (the registry? I can't remember - it was one of those late night the night before we're supposed to ship conversations with John)
Yes, there needs to be a decision whether or not nsnotify.exe: 1) will be in Netscape branded mozilla.org 2) if so, will it be enhanced to work with the new features and code (Also, is this bug really talking about nsnotify.exe? Look like it was reported against Solaris which doesn't have nsnotify.)
The platform field in bugsplat #334286 was erroneous.
Whiteboard: [Perf]
Putting on [Perf] radar.
Assignee: phil → mscott
Sounds like an IMAP protocol issue. We should also have a high-level design for nsnotify based on the new Seamonkey code for prefs, protocol, etc.
Whiteboard: [Perf] → [Perf] nsnotify's future is unclear
Leaving without target for now since nsnotify's future is unclear.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → WONTFIX
nsnotify was recently put on the "OUT" list. Moving nug to Resolved/Won't Fix. phil, if agreed, please mark Verified.
Status: RESOLVED → REOPENED
Status: REOPENED → RESOLVED
Closed: 25 years ago25 years ago
Resolution: WONTFIX → LATER
I vote for Later rather than Wontfix. NsNotify could certainly resurface in a later rev if it's important.
Status: RESOLVED → VERIFIED
Summary: mail notification client uses short IMAP sessions → nsnotify: mail notification client uses short IMAP sessions
verified as later.
Moving all Mail/News Networking bugs to Mail/News Networking-Mail This may re-open previously Verified bugs due to a Bugzilla bug...if so, I will fix those bugs.
nsnotify or "MozNotify" would be a VERY useful feature for the user. I kindly request that you try to implement this valuable feature in mozilla0.8. Everyone will appreciate being notified when new mail has arrived, even if mozilla is not running or if it is minimized or behind another app.
LATER is deprecated per bug 35839.
Status: VERIFIED → REOPENED
Resolution: LATER → ---
Product: MailNews → Core
Assignee: mscott → nobody
Status: REOPENED → NEW
QA Contact: fenella → mailnews.networking
WONTFIXing, since nsnotify is long dead and both SeaMonkey and Thunderbird support various notifications, so "minimized" or "behind another app" are no issues. (SM trunk can even biff without running an actual mailnews window.)
Status: NEW → RESOLVED
Closed: 25 years ago16 years ago
Resolution: --- → WONTFIX
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.