| components.conf |
|
2190 |
| EwsClient.h |
|
475 |
| EwsFolder.cpp |
|
10015 |
| EwsFolder.h |
|
2268 |
| EwsIncomingServer.cpp |
Creates a new folder with the specified parent, name, and flags.
|
10067 |
| EwsIncomingServer.h |
|
2075 |
| EwsMessageChannel.cpp |
|
8814 |
| EwsMessageChannel.h |
|
1661 |
| EwsProtocolHandler.cpp |
|
1409 |
| EwsProtocolHandler.h |
|
549 |
| EwsProtocolInfo.cpp |
|
4382 |
| EwsProtocolInfo.h |
|
534 |
| EwsService.cpp |
|
7530 |
| EwsService.h |
|
660 |
| IEwsClient.idl |
Create a new message on the server using the data read from the stream.
@param folderId The EWS ID of the folder.
@param isDraft Whether the message being created is an unsent
draft.
@param messageStream The input stream to read the message from.
@param copyListener A listener to provide updates on copying of
the message from the stream.
@param messageCallbacks Callbacks to use to communicate between the EWS
client and the EWS folder (e.g. to access its
database).
|
2859 |
| IEwsIncomingServer.idl |
IEwsIncomingServer is intended as a workaround for limitations in the folder
lookup service.
EWS folders require an EWS client object in order to fetch new messages. The
folder itself, however, does not have access to all of the details needed to
create such a client. This information is part of the incoming server.
Due to depending on the folder lookup service to create new folders, it is
not possible to give the folder a direct handle to its associated server, so
we are forced to go through XPCOM.
|
922 |
| moz.build |
|
797 |
| nsEwsOutgoingServer.h |
|
652 |