| 1 |
======================== |
| 2 |
|
| 3 |
1. BUILD |
| 4 |
|
| 5 |
$ cd .../sources/evolution-ews |
| 6 |
$ mkdir build |
| 7 |
$ cd build |
| 8 |
$ cmake -G "Unix Makefiles" \ |
| 9 |
-DCMAKE_INSTALL_PREFIX=/opt/evolution \ |
| 10 |
-DCMAKE_BUILD_TYPE=Release \ |
| 11 |
.. |
| 12 |
$ make -j |
| 13 |
$ make -j install |
| 14 |
|
| 15 |
Run `cmake --help` to get list of available generators (the -G argument) |
| 16 |
on your platform. |
| 17 |
|
| 18 |
======================== |
| 19 |
|
| 20 |
2. Test Suite |
| 21 |
|
| 22 |
Pre-requisites to launch the test suite. |
| 23 |
Export the following environmental variables for your test suite to run. |
| 24 |
|
| 25 |
EWS_TEST_USERNAME |
| 26 |
EWS_TEST_PASSWORD |
| 27 |
EWS_TEST_EMAIL |
| 28 |
EWS_TEST_URI |
| 29 |
|
| 30 |
$ make check |
| 31 |
|
| 32 |
========================= |
| 33 |
|
| 34 |
3. Autodiscover reference |
| 35 |
|
| 36 |
The Autodiscover service provides the configuration information necessary to |
| 37 |
create a connection to an Exchange server. The Autodiscover service provides |
| 38 |
a mechanism that allows you to use “plain old XML” (POX) messages — that is, |
| 39 |
messages that consist solely of XML payloads without any enclosing SOAP |
| 40 |
envelopes — to locate the settings that a client application must have in |
| 41 |
order to connect to Exchange. |
| 42 |
|
| 43 |
Currently the test suite uses autodiscovery to fetch the url to connect to, |
| 44 |
using your username and email provided. |
| 45 |
|
| 46 |
Reference: |
| 47 |
http://msdn.microsoft.com/en-us/library/aa581522.aspx |
| 48 |
|
| 49 |
The ASUrl (POX) element contains the url. Use this for all subsequent requests |
| 50 |
to your Exchange server. |
| 51 |
|
| 52 |
A typical ASUrl looks like this, |
| 53 |
https://server_ip/EWS/Exchange.asmx |
| 54 |
|
| 55 |
========================== |
| 56 |
|
| 57 |
4. URLs |
| 58 |
|
| 59 |
-> Development overview - http://msdn.microsoft.com/en-us/library/cc535017%28v=EXCHG.80%29.aspx |
| 60 |
|
| 61 |
-> Autodiscover reference - http://msdn.microsoft.com/en-us/library/aa581522.aspx |
| 62 |
|
| 63 |
-> EWS XML Elements - http://msdn.microsoft.com/en-us/library/aa580675%28v=EXCHG.80%29.aspx |
| 64 |
|
| 65 |
=========================== |
| 66 |
|
| 67 |
5. Address book |
| 68 |
|
| 69 |
Fetching Global address list |
| 70 |
|
| 71 |
Use OAB (Offline Address Book) for caching the GAL locally into Evolution. |
| 72 |
|
| 73 |
While caching happens in the background, until the cache is setup, use |
| 74 |
Resolve Names. |
| 75 |
|
| 76 |
Resolve names operation |
| 77 |
http://msdn.microsoft.com/en-us/library/aa563518(v=EXCHG.80).aspx |
| 78 |
|
| 79 |
Unresolved Entry |
| 80 |
http://msdn.microsoft.com/en-us/library/aa581054(v=EXCHG.80).aspx |
| 81 |
|
| 82 |
============================ |
| 83 |
|
| 84 |
6. Fetching Public folders |
| 85 |
|
| 86 |
Needs an additional header not mentioned in the documentation |
| 87 |
Include the following header for Exchange 2007, |
| 88 |
<soap:Header> |
| 89 |
<t:RequestServerVersion Version="Exchange2007_SP1"/> |
| 90 |
</soap:Header> |
| 91 |
|
| 92 |
What's the equivalent for Exchange 2010? No server to test as yet. |
| 93 |
|
| 94 |
============================= |
| 95 |
|
| 96 |
7. Ideas yet to research on |
| 97 |
|
| 98 |
== Mailer == |
| 99 |
|
| 100 |
Following the IMAPX backend, we could make EWS asynchronous in the same manner |
| 101 |
prioritizing the client requests. |
| 102 |
|
| 103 |
Separate out the prioritizing client requests and make it common to all |
| 104 |
providers. |
| 105 |
|
| 106 |
Is pipe-lining requests possible? |
| 107 |
|
| 108 |
|
| 109 |
|
| 110 |
== Calendar == |
| 111 |
|
| 112 |
Make the operations similar to mailer. Handle all the operations Offline and |
| 113 |
later sync it with server. |
| 114 |
|
| 115 |
Handle all the offline operations in a single class, say CalBackendOffline. |
| 116 |
Cache needs to be extended to be able to give the list of un-syncronized |
| 117 |
(local->server) items. We could handle the error messages for the |
| 118 |
un-synchronized calendar items (eg: meeting created) by optionally displaying |
| 119 |
an error dialog and also providing a visual cue in the form of an icon. |
| 120 |
|
| 121 |
The error can also be logged per event. Eg: Opening the meeting can show the |
| 122 |
actual error in the meeting editor in a non-intrusive manner. This very similar |
| 123 |
to how mailer handles the un-sent mails in OutBox showing the error messages. |
| 124 |
|
| 125 |
Improve FreeBusy performance by fetching free/busy information for all users at |
| 126 |
a single stretch if the server supports it. FreeBusy requests should be |
| 127 |
cancellable. Provide EDS ECal apis for the same. |
| 128 |
|
| 129 |
|
| 130 |
== Address book == |
| 131 |
|
| 132 |
Ensure the auto-completion performance doesn't fade while caching the contacts |
| 133 |
or fetching deltas. |
| 134 |
|
| 135 |
other improvement areas? |
| 136 |
|
| 137 |
|
| 138 |
== Single Connection (to be analyzed) == |
| 139 |
|
| 140 |
Are multiple connections allowed on exchange servers or is there any limit ? |
| 141 |
Since address-book, calendar, mailer are run as separate processes we would |
| 142 |
require three connections if connections are not shared. |
| 143 |
|
| 144 |
If we want to use a single connection, we might need to write ews connection |
| 145 |
layer as a separate process and let mailer,e-address-book-factory, |
| 146 |
e-calendar-factory send the requests to it. |