Closed Bug 68651 Opened 25 years ago Closed 24 years ago

streamConverter should use NS_LITERAL_STRING

Categories

(Core Graveyard :: Networking: FTP, defect)

x86
Linux
defect
Not set
trivial

Tracking

(Not tracked)

VERIFIED FIXED
mozilla1.0

People

(Reporter: bbaetz, Assigned: bbaetz)

References

()

Details

Attachments

(2 files)

While looking at the ftp changes, I noticed that its doing a whole lot of .AssignWithConversion("String constant"), instead of using NS_LITERAL_STRING. The above URL is one example, but there are others.
Target Milestone: --- → Future
Attached patch patchSplinter Review
+ nsAutoString fromStr; fromStr.Assign(NS_LITERAL_STRING("text/ftp-dir-")); nsAutoString fromStr(NS_LITERAL_STRING("text/ftp-dir-")); is slightly more efficient. r=jag Is there a bug yet on localizing those lines you're touching?
OK, new patch coming up. > Is there a bug yet on localizing those lines you're touching? don't know. I filed a bug (which got helpwanted and FUTUREd) on printing the server's actual reply though. If I do that, that string won't be localised.
Attached patch new patchSplinter Review
r=jag
Make sure it works on windows. I once had problems compiling on windows with the NS_LITERAL_STRING. I had to use a .get(). Ensure that and sr=dougt. can I get you to look at the ftp stream converter :-)
I'll look at the stream converter, and get a windows person to look at this patch. I'm building with -fshort-wchar, so I should be getting the same types of strings that the windows people are. One thing I noticed is that the streamconverter handles a whole lot of ftp server types which aren't handled by the ftp protocol handler. Am I missing something?
Status: NEW → ASSIGNED
Oh, and reassigning so that I can find it when I get arround to applying for CVS write access.
Assignee: dougt → bbaetz
Status: ASSIGNED → NEW
The ftp implemention (protocol and converter) were based on the classic code which "supported" more ftp servers then what mozilla does. I bet this mismatch is because we did not removed some of the server type from the converter. No harm, i guess.
But you added VMS into the stream converter with the big necko branch landing, but didn't touch the protocol handler. It doesn't matter, I suppose.
walk84 compiled it on windows with no problems.
Status: NEW → ASSIGNED
jag checked the fix in for me. I'll leave this open for the stream converter changes. Oh, and ignore what I was talking about wrt VMS. Don't know where I got that from.
The streamConverter stuff would benefit from the new strings, I think. I'll fix this when that lands.
Summary: nsFtpConnectionThread should use NS_LITERAL_STRING → nsFtpConnectionThread/streamConverter should use NS_LITERAL_STRING
Target Milestone: Future → mozilla0.9
Morphing.
Summary: nsFtpConnectionThread/streamConverter should use NS_LITERAL_STRING → streamConverter should use NS_LITERAL_STRING
Target Milestone: mozilla0.9 → mozilla0.9.1
Done as part of bug 78148
Depends on: 78148
pushing off - this is too late for 0.9.1
Target Milestone: mozilla0.9.1 → mozilla0.9.2
Target Milestone: mozilla0.9.2 → mozilla1.0
QA Contact: tever → benc
Mass change: Bug 78148 has been checked in, and so it and these dependancies should have been fixed. If you disagree, please reopen. Note that the xul view is still enabled for file because of i18n problems. The bug to fix this is bug 102812.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
jag or dougt: since this is purely a code change (no external black-box test), would one of you mark this verified?
VERIFIED: Poked around in the URL provided (in LXR) and couldn't find any of the offending code.
Status: RESOLVED → VERIFIED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: