Closed
Bug 31241
Opened 26 years ago
Closed 7 years ago
backend URI cleanup - switch to using native mail objects instead of passing around URI strings
Categories
(MailNews Core :: Backend, defect, P2)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: alecf, Unassigned)
References
Details
Attachments
(1 file, 1 obsolete file)
|
5.11 KB,
patch
|
Details | Diff | Splinter Review |
This is the master bug for the URI cleanup I'm doing for mail.
I'll mostly use this bug to attach patches/etc so I can test my stuff on
multiple machines and platforms.
| Reporter | ||
Comment 2•26 years ago
|
||
| Reporter | ||
Comment 3•26 years ago
|
||
| Reporter | ||
Updated•26 years ago
|
Status: NEW → ASSIGNED
Priority: P3 → P2
Target Milestone: M17
| Reporter | ||
Updated•26 years ago
|
Target Milestone: M17 → M20
| Reporter | ||
Comment 4•25 years ago
|
||
reassign to sspitzer - this is the bit about switching over to using native mail
objects instead of passing around URI strings. come see me if you want to know
what this is about... this can be done in many stages.
my patches above are checked in, I believe
Assignee: alecf → sspitzer
Status: ASSIGNED → NEW
Comment 5•24 years ago
|
||
Seth told me to file a bug on mailnews uri cleanup when I was talking to him the
other day.
I guess this bug will do instead :)
You need to make sure that all protocols you have which ever get to necko in any
way are registered with a necko protocol handler, too.
Comment 6•24 years ago
|
||
This is blocking mime service work... we need to be able to Clone() uris and
mailnews ones are not Clone()-able. (see bug 78943, comment #35). I'm not sure
we ever really deal with mailnews uris in that code, but I'd rather not break,
say, attachment handling by accident. :)
Blocks: 78943
Updated•23 years ago
|
QA Contact: lchiang → stephend
Comment 7•23 years ago
|
||
Is this ready for review?
Comment 8•23 years ago
|
||
Last comment bugmail "Excluding: sspitzer@netscape.com,..."
Therefore, setting this to 1.6a in hopes that it gets reviewed before 1.7 work.
Target Milestone: --- → mozilla1.6alpha
Comment 9•23 years ago
|
||
Those diffs are against files that don't seem to even exist anymore (got
renamed? removed?)
Target Milestone: mozilla1.6alpha → ---
Comment 10•23 years ago
|
||
date: 2001/03/17 02:54:07; author: sspitzer%netscape.com; state: dead; lines:
+0 -0
remove files no longer part of the build due to the mailnews landing.
(specifically, there is no more message datasource or nsIMessage)
This is the last log message for all three patched files.
Therefore, marking INVALID.
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → INVALID
Comment 11•23 years ago
|
||
Uh-huh. Except those patches were just the _first_ patches for this bug. See
comment 0 or something. Mailnews URI implementations still need to be fixed, as
we move to separate apps, if only because once mailnews is a separate app, necko
and core layout components should NOT be working around bugs in it any more (and
I will probably start removing such workarounds if I modify the relevant code).
So we really do want to fix this.
Status: RESOLVED → REOPENED
Resolution: INVALID → ---
Updated•21 years ago
|
Product: MailNews → Core
Comment 12•19 years ago
|
||
sorry for the spam. making bugzilla reflect reality as I'm not working on these bugs. filter on FOOBARCHEESE to remove these in bulk.
Assignee: sspitzer → nobody
Status: REOPENED → NEW
| Assignee | ||
Updated•18 years ago
|
Product: Core → MailNews Core
Comment 14•8 years ago
|
||
Does this (and the patches) have any value eighteen years later with today's code.
Flags: needinfo?(acelists)
Summary: backend URI cleanup → backend URI cleanup - switch to using native mail objects instead of passing around URI strings
Comment 15•7 years ago
|
||
The attached patches do not really do much.
But I'd forward to Jorg who is familiar with our mailnews URIs.
Flags: needinfo?(acelists) → needinfo?(jorgk)
Updated•7 years ago
|
Attachment #6347 -
Attachment is obsolete: true
Flags: needinfo?(jorgk)
Comment 16•7 years ago
|
||
I don't understand what the aim is here. Something like this
-NS_IMETHODIMP nsMessage::GetMime2DecodedSubject(nsString *resultSubject)
+NS_IMETHODIMP nsMessage::GetMime2DecodedSubject(PRUnichar* *resultSubject)
is certainly an r- since there's no way we're going from a smart string to a raw string.
Let's close this.
Status: NEW → RESOLVED
Closed: 23 years ago → 7 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•