Closed Bug 102266 Opened 23 years ago Closed 22 years ago

Use copyService rather than directly using copyMessages routine

Categories

(MailNews Core :: Backend, defect, P2)

Product:
MailNews Core
Component:
Backend
Platform:
x86
Windows NT
Type:
defect

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: naving, Assigned: naving)

References

Details

This is essential to serialize more than one copy request.
Thanks blizzard for pointing out this problem.
Status: NEW → ASSIGNED
-> blizzard@mozilla.org
Assignee: naving → blizzard
Status: ASSIGNED → NEW
Did you mean to reassign this bug. It will cover all of mailnews. I think you
intended to reassign bug 102178. 
Oh, I thought you wanted me to tackle this.
-> naving
Assignee: blizzard → naving
besides copying to the sent folder what are some of the other areas that will be
affected by this fix?
practically everything that involves a copy operation. This is the one of 
the major code clean-up that needs to be done.
Keywords: nsbeta1
Keywords: nsbeta1 → nsbeta1+
Priority: -- → P2
Blocks: 122274
Status: NEW → ASSIGNED
Keywords: nsbeta1+ → nsbeta1-
No longer blocks: 122274
I am in the middle of doing this because I need it for drag and drop of search
results to mail3pane.
I have rerouted most of the copies thru copy service, we still need to do some
like from nsMsgDBView and take care of delete msgs, will do it later. marking
this fixed 
because it was mainly filed for fcc copies
Status: ASSIGNED → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
verified
Status: RESOLVED → VERIFIED
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.