aboutsummaryrefslogtreecommitdiffhomepage
path: root/src/cmake/async.cmake
diff options
context:
space:
mode:
authorGravatar Michael Lenaghan <michaell@dazzit.com>2014-10-24 17:56:49 -0400
committerGravatar Michael Lenaghan <michaell@dazzit.com>2014-10-24 20:33:20 -0400
commitec1da36eaf2adfb5695f5c0d8ca92d23d31b56a5 (patch)
tree3c57763f4b3fe597a0d28f70d3634b36542dc663 /src/cmake/async.cmake
parentd0b53a64bdbeaa71d80210640534abea1a85f8d2 (diff)
Add an operation to fetch a parsed message.
This avoids the copying of Data to NSData to Data which happens with the current approach. In one test case, a message with an ~18 MB attachment, the current (copying) approach peaked at ~150 MB of memory usage in my app. This new approach peaks at ~65 MB. Another test case, which often caused iOS to terminate my app, now peaks at ~90 MB. In addition to the improved memory usage this approach also means that message parsing is performed asynchronously.
Diffstat (limited to 'src/cmake/async.cmake')
-rw-r--r--src/cmake/async.cmake1
1 files changed, 1 insertions, 0 deletions
diff --git a/src/cmake/async.cmake b/src/cmake/async.cmake
index 58f410d4..947a69ee 100644
--- a/src/cmake/async.cmake
+++ b/src/cmake/async.cmake
@@ -13,6 +13,7 @@ set(async_imap_files
async/imap/MCIMAPDisconnectOperation.cc
async/imap/MCIMAPExpungeOperation.cc
async/imap/MCIMAPFetchContentOperation.cc
+ async/imap/MCIMAPFetchParsedContentOperation.cc
async/imap/MCIMAPFetchFoldersOperation.cc
async/imap/MCIMAPFetchMessagesOperation.cc
async/imap/MCIMAPFetchNamespaceOperation.cc