Thanks to Stephen Walker <walk84@yahoo.com> for the patch.
Bug #172898 r=cls a=asa
git-svn-id: svn://10.0.0.236/trunk@132136 18797224-902f-48f8-a5cc-f745e15eee43
use "_moz_mailbeep". on windows, we map this to "MailBeep" (so it works on win2k and win98)
and on mac we use sfraser's code to go to internet config. (nothing on linux yet, that's another bug)
r=pinkerton, sr=sfraser
also, fix#104252. selectively notify folder listeners. when we register the folder listener
with the mail session, we pass in flags for what types of things we care about.
this reduces the notifications, especially those across XPConnect.
r=bienvenu, sr=mscott
git-svn-id: svn://10.0.0.236/trunk@105195 18797224-902f-48f8-a5cc-f745e15eee43
r=pavlov, sr=bienvenu. right now, this only works on windows.
mac is next. for linux (and the other platforms), we currently beep.
if there isn't an OS specified sound, we'll play the pre-packaged
sound that mailnews will eventually ship with.
git-svn-id: svn://10.0.0.236/trunk@105027 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
into a buffer, and then sends it to win32 PlaySound to play asynchronously. r=nisheeth r=hyatt.
git-svn-id: svn://10.0.0.236/trunk@55292 18797224-902f-48f8-a5cc-f745e15eee43
