I've just finished the framework of the Message Transport. I started
over when someone (maybe that was Charles? I can't find the email
now) pointed me to a much better, and recent, MessageTransport
provider example on one of the MDSN blogs. It had a few advantages:
cleaner code, modern code, well documented. I think my new version
will also have fewer copyright issues, if any, because none of the
actual code was copied verbatim (though I used their logging system,
but that's somewhat easy to replace once this is installed in the
OpenConnector codebase).
I'm at the point where Outlook starts up, tells it to flush its
inbound and outbound messages, and then it seems to shutdown. I'd
like to watch the status change, and I've implemented a MAPIStatus
subclass, but I'm not sure where in Outlook I can actually observe
the status of the message transport, and what state its in (part of
the status row includes human-readable text associated with the
current status code).
Starting next week, I'll be working on adding CalDAV calls to the
code. If anyone has more insights into how Outlook deals with
calendar data, especially in terms of addressability, this is the
time to share them. :) The only thing we suspect at this point is
that they are CDO objects, but I haven't seen Outlook ever try to
send them through a Message Transport. That may be a function of
where the transport is placed in the MAPISVC file... haven't tried
playing with that yet.
Mark
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
otlkcon-devel mailing list
otlkcon-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/otlkcon-devel
