Open
Bug 74702
Opened 24 years ago
Updated 2 years ago
batch the updates when getting new mail (pop)
Categories
(MailNews Core :: Networking: POP, enhancement)
MailNews Core
Networking: POP
Tracking
(Not tracked)
UNCONFIRMED
People
(Reporter: sspitzer, Unassigned)
Details
(Keywords: perf)
batch the updates when getting new mail (pop) right now, we update the unread count on the inbox on every new mail
Comment 2•24 years ago
|
||
Not sure if we're doing it for imap - this may not be so important if we use the rdf-outliner in the folder pane.
Comment 3•23 years ago
|
||
I'm going to mark this nsbeta1-. If we think we can get a big savings on this then we can reopen it. When we open a folder I think we are ok (correct me if I'm wrong) so this is mostly for the case when the user hits Get Msgs which generally shouldn't have too many new messages coming in.
Reporter | ||
Comment 4•23 years ago
|
||
right, it's not too big a deal. 4.x doesn't batch these updates. future is the proper milestone. but one day...
Updated•20 years ago
|
Product: Browser → Seamonkey
Updated•19 years ago
|
Assignee: sspitzer → mail
Updated•16 years ago
|
Assignee: mail → nobody
Severity: normal → enhancement
Component: MailNews: Message Display → MailNews: Backend
QA Contact: esther → mailnews-backend
Hardware: PC → All
Target Milestone: Future → ---
Comment 5•15 years ago
|
||
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614
Status: NEW → UNCONFIRMED
Comment hidden (duplicate) |
Comment hidden (duplicate) |
Comment hidden (duplicate) |
Comment hidden (duplicate) |
Comment hidden (duplicate) |
Updated•15 years ago
|
Component: MailNews: Backend → Networking: POP
Ever confirmed: false
Keywords: perf
Product: SeaMonkey → MailNews Core
QA Contact: mailnews-backend → networking.pop
Version: Trunk → unspecified
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•