| moz.build |
|
835 |
- |
| nsIAutoSyncFolderStrategy.idl |
Returns a relative-priority for the second folder by comparing with the first one.
|
725 |
- |
| nsIAutoSyncManager.idl |
Queue types
|
5357 |
- |
| nsIAutoSyncMsgStrategy.idl |
Returns a relative-priority for the second message by comparing with the first message.
|
1180 |
- |
| nsIAutoSyncState.idl |
Auto-Sync states.
***WARNING***: If you change these, be sure to update stateStrings in
nsAutoSyncState.cpp. If you do not, out-of-bounds memory accesses may
happen.
|
4481 |
- |
| nsIImapFlagAndUidState.idl |
If a full update, the total number of deleted messages
in the folder; if a partial update, the number of deleted
messages in the partial update
|
3310 |
- |
| nsIImapHeaderXferInfo.idl |
|
1222 |
- |
| nsIImapHostSessionList.h |
|
6023 |
- |
| nsIImapIncomingServer.idl |
delete with a big red x |
3978 |
- |
| nsIImapMailFolderSink.idl |
nsIImapMailFolderSink provides a way for the IMAP system to communicate
with the local folder representation.
The IMAP system could poke folders directly, but going through this
interface has a couple of benefits:
1. It better defines the public coupling between the two systems.
2. It's easier to wrap with a proxy class so the IMAP system can safely
call the methods across thread boundaries (see ImapMailFolderSinkProxy).
|
5329 |
- |
| nsIImapMessageSink.idl |
nsIImapMessageSink provides a way for the IMAP system to exchange
message-related information with the local folder representation.
The IMAP system could poke folders directly, but going through this
interface has a couple of benefits:
1. It better defines the public coupling between the two systems.
2. It's easier to wrap with a proxy class so the IMAP system can safely
call the methods across thread boundaries (see ImapMessageSinkProxy).
|
4078 |
- |
| nsIImapMockChannel.idl |
Because imap protocol connections (which are channels) run through a cache,
it isn't always the case that when you want to run a url, you actually get
a connection back right away. Often times, the url goes into a queue until
a connection becomes available.
Unfortunately, if we want to be a truly pluggable protocol with necko, necko
requires the ability to get a channel back right away when it wants to run
a url. It doesn't let you wait until an imap connection becomes available.
So I've created the notion of a "mock channel". This mock channel is what
gets returned to necko (or other callers) when they ask the imap service
for a new channel for a url. The mock channel has "mock" implementations
of nsIChannel. Eventually, when we actually assign the url to a real
channel, we set the real channel on the mock channel. From that point forward,
the mock channel forwards channel calls directly to the real channel.
In short, this class is how I'm solving the problem where necko wants
a channel back as soon as they ask for when with the fact that it
may be a while until the url is loaded into a connection.
|
2110 |
- |
| nsIImapOfflineSync.idl |
|
992 |
- |
| nsIImapProtocol.idl |
Set up this connection to run a URL.
Called by nsImapIncomingServer to process a queued URL when it spots a
free connection.
Because nsImapProtocol is really a connection and doesn't follow the
usual nsIChannel lifecycle, this function is provided to allow reuse.
Over and over again.
|
3278 |
- |
| nsIImapProtocolSink.idl |
Helper interface that contains operations MUST be proxied
over UI thread.
|
862 |
- |
| nsIImapServerSink.idl |
nsIImapServerSink is designed to be used as a proxy to the application's UI
thread from the running IMAP threads.
|
8125 |
- |
| nsIImapService.idl |
Most of the nsIImapService methods are friendly front ends for composing and
issuing "imap://" protocol operations. Usually a nsImapUrl will be returned.
This url object is stateful and tracks the issued request.
|
10035 |
- |
| nsIImapUrl.idl |
copyState is used by some IMAP copy operations. The exact type stashed
here depends on the operation being performed. For online move/copy,
it'll be an nsImapMailCopyState (private to nsImapMailFolder). For
other operations it might be (say), an nsIStreamListener.
|
8979 |
- |
| nsIMailboxSpec.idl |
The highest modification sequence number the parser has seen
for this mailbox. See IMAP RFC 4551
|
1374 |
- |
| nsIMsgImapMailFolder.idl |
nsIMsgQuota defines the quota for a resource within a quota root.
@see RFC 2087
|
9968 |
- |