On Wed, 2011-02-09 at 13:04 +0100, Milan Crha wrote:
> never mind, I found it, it wasn't so hard as I expected, finally. I'll
> give it a try and report back if I'll have any issue or concern with it.
Hi again,
so I did some tests and fetching with FXCopyMessages is significantly
faster, comparing it downloading all the bits of messages, not only its
properties, but also attachments and other, then it's still not the
exact thing I would like to have. Not talking about that I feel like
misusing the function, because I'm actually not going to copy messages
anywhere, I'm only reading its properties.
My only concern is that I would like to have something between
FXCopyMessages and FXCopyProperties, an option to ask for particular
messages, but only some properties from them, without attachments and
such, for a summary fetching. We use quite limited list of properties
for summary, so avoiding download of "all" properties, and subobjects is
the main goal. Of course, FXCopyProperties is not usable because it
requires particular object, which means OpenMessage/mapi_object_release
calls, which are also pretty slow.
Do you have any idea?
Thanks and bye,
Milan
P.S.: Here's a list of properties we fetch for summary, and as you can
see not all of them can be fetches within the content table, so it
forces us to do OpenMessage call with GetProps.
PR_INTERNET_CPID,
PR_SUBJECT_UNICODE,
PR_MESSAGE_SIZE,
PR_MESSAGE_DELIVERY_TIME,
PR_MESSAGE_FLAGS,
PR_SENT_REPRESENTING_NAME_UNICODE,
PR_SENT_REPRESENTING_EMAIL_ADDRESS_UNICODE,
PR_SENT_REPRESENTING_ADDRTYPE_UNICODE,
PR_LAST_MODIFICATION_TIME,
PR_INTERNET_MESSAGE_ID,
PR_INTERNET_REFERENCES,
PR_IN_REPLY_TO_ID,
PR_DISPLAY_TO_UNICODE,
PR_DISPLAY_CC_UNICODE,
PR_DISPLAY_BCC_UNICODE,
PR_TRANSPORT_MESSAGE_HEADERS_UNICODE
_______________________________________________
devel mailing list
[email protected]
http://mailman.openchange.org/listinfo/devel
