- combine nsICharsetConverterManager2 and nsICharsetConverterManager
- get rid of nsIAtom in most of the methods
- provide versions of getUnicodeDecoder/Encoder which don't do alias resolution
- change all charset types to ASCII strings
- clean up some other i18n APIs which could be simplified
- fix all consumers of all changed i18n interfaces
r=jshin, smontagu
rs=sfraser
git-svn-id: svn://10.0.0.236/trunk@143589 18797224-902f-48f8-a5cc-f745e15eee43
fix for smoketest blocker #110478. reply to local messages fails to quote the message.
calling SetSpec() on a spec with a query string causes problems. see #110508
but to fix the blocker, I've rewritten the code to use SetQuery(), which is better anyways.
r=ducarroz
git-svn-id: svn://10.0.0.236/trunk@108324 18797224-902f-48f8-a5cc-f745e15eee43
using a combination of nsCOMPtr and nsWeakReferences
r=varada
sr=sspitzer
git-svn-id: svn://10.0.0.236/trunk@101694 18797224-902f-48f8-a5cc-f745e15eee43
This removes all call-sites I can currently fix. Tomorrow I'll try to get someone to checkin my changes to security/ and I'll get some help with the Netscape side of things.
nsString::GetUnicode()'s final death-blow will be dealt soon. Please keep this in mind as you add new code :-)
git-svn-id: svn://10.0.0.236/trunk@98363 18797224-902f-48f8-a5cc-f745e15eee43
Includes front end re-write to use the outliner widget for the thread pane.
Improvements in scrolling, folder loading, message display, replyto time, sorting, selecting, deleting, the list goes
on and on.
enjoy =).
git-svn-id: svn://10.0.0.236/trunk@89742 18797224-902f-48f8-a5cc-f745e15eee43
Revising nsIChannel to allow for overlapped i/o. This consists of three parts:
1. Factoring nsIChannel into a protocol specific part, the nsIChannel, and a socket specific, the nsITransport.
2. Derive the nsIChannel from a nsIRequest.
2. Changes the notification system from necko and the URILoader to pass the nsIRequest interface instead of nsIChannel interface.
This goal stems from wanting to be able to have active AsyncRead and AsyncWrite operations on nsSocketTransport.
This is desired because it would greatly simplify the task of maintaining persistent/reusable socket connections
for FTP, HTTP, and Imap (and potentially other protocols). The problem with the existing nsIChannel interface is
that it does not allow one to selectively suspend just one of the read or write operations while keeping the other active.
r=darin@netscape.comsr=rpotts@netscape.com
git-svn-id: svn://10.0.0.236/trunk@87587 18797224-902f-48f8-a5cc-f745e15eee43
1. Factoring nsIChannel into a protocol specific part, the nsIChannel, and a socket specific, the nsITransport.
2. Derive the nsIChannel from a nsIRequest.
2. Changes the notification system from necko and the URILoader to pass the nsIRequest interface instead of nsIChannel interface.
This goal stems from wanting to be able to have active AsyncRead and AsyncWrite operations on nsSocketTransport.
This is desired because it would greatly simplify the task of maintaining persistent/reusable socket connections
for FTP, HTTP, and Imap (and potentially other protocols). The problem with the existing nsIChannel interface is
that it does not allow one to selectively suspend just one of the read or write operations while keeping the other active.
The full details of the change on written up in the netlib newsgroup.
r=darin@netscape.comsr=rpotts@netscape.com
git-svn-id: svn://10.0.0.236/trunk@86717 18797224-902f-48f8-a5cc-f745e15eee43
the message for quoting purposes. As a result, the content type (which includes the charset information for the message)
was not getting set on the right channel. I changed things so we pass in the real channel and not a bogus one.
r=alecf
git-svn-id: svn://10.0.0.236/trunk@74119 18797224-902f-48f8-a5cc-f745e15eee43
