You won't need Exchange, so that should help simplify the environment. You won't need to inspect packets either. You will need to inspect assembly. Are you familiar with MAPI internals at all? Or IDA Pro and Assembly Language?
I really only ever used a CalDAV server for testing. We can use Bedework ( http://bedework.com/ ) for this. If you plan on working on migrating the datalayer to C#, then you won't need a server at all. All the testing can be done locally. If you plan to work on shared folders support then you will need IDA Pro and lots, and lots of patience :) Unfortunately, there isn't much documentation. But I will be happy to answer any questions you may have. The role of the datalayer is to save MAPI data. This is what saves appointments and messages to the disk. It is only used by a very small number of interfaces. Actually IMAPIProp (http://otlkcon.svn.sourceforge.net/viewvc/otlkcon/trunk/otlkcon/opncon/O_IProp.cpp?view=markup ) and IMAPITable being the biggest consumers. Currently, it uses an SQLite database. We should move this to SQL Server Compact for better locking, application transaction model and more support for platform database abstraction features. Again, feel free to ask as many questions as you'd like. I will try to clarify things as best as I can. Best regards, Kervin From: g...@novadsp.com [mailto:g...@novadsp.com] Sent: Wednesday, July 22, 2009 7:09 AM To: Kervin Pierre Cc: firstname.lastname@example.org Subject: Re: [otlkcon-devel] Status? Hello Kervin Over the next few months I could put some real effort into things. I'm still in the process of establishing what Scalix can do, for example. Over the two weeks or so, practically zero. got a wedding and a hundredth birthday. neither of which are mine but involve large & complex gatherings :) I propose: 1. Be able to build the current OC source snap. I pulled trunk using SVN. 2. Get the connector running in parallel with the Scalix binary - a Linux box is possibly easier to use for inspecting packets. I also have Ex03 running here on W2003. 3. Asking questions. So: What role does the current data layer play in OC? Please point me to any relevant URLs for docs I can read in the interim. ATB Jerry Kervin Pierre wrote: Hello, This is great news. How much time do you believe you can put towards the project? The most important work needed at this time is the figuring out how Outlook loads and uses a shared calendar. Coincidently, this is why the Exchange MAPI SDK was pulled in. I don't think much or any of it is used except for the header files. Figuring that out would require really good IDA Pro skills; No or little programming. The libraries used are from the Exchange MAPI download. I think it's at http://www.microsoft.com/downloads/details.aspx?FamilyID=e17e7f31-079a-43a9-bff2-0a110307611e&DisplayLang=en now, but I can't confirm on my current computer. I have Ex2kSdk.lib, Ex2KSdkD.lib and sadapi.lib in the ExchangeSDK\Lib folder. Another thing that I would like to do is to move the data layer from C++/SQLite to C#/SQL Server Compact and use COM+ to communicate with Outlook. If we can get the performance we need for from that setup then that would help with getting new developers in the future. Best regards, Kervin From: g...@novadsp.com<mailto:g...@novadsp.com> [mailto:g...@novadsp.com] Sent: Tuesday, July 21, 2009 5:17 PM To: Kervin Pierre Cc: email@example.com<mailto:firstname.lastname@example.org> Subject: Re: [otlkcon-devel] Status? Hello Kervin I can actively participate in development - I'm trying to establish what OC needs to get built. Which Exchange SDK are you using for the current release? Although the calendar aspect is good I'm most keen to get shared tasks up & running. Sadly cannot help with funding - indeed could use some myself :) When I get Zimbra configured I will get a chance to test their connector - right now it's an MX mess :\ Any info gratefully received G. Kervin Pierre wrote: Hello, I am unable to put in anytime into the project at this time, and no one has stepped in to continue or fund development. So I would have to say the project is stalled until this situation changes. Open Connector is primarily a CalDAV connector. So I think your best bet would be to go with one of the commercial offerings out there like Zimbra Connector or ZideOne. Best regards, Kervin From: g...@novadsp.com<mailto:g...@novadsp.com> [mailto:g...@novadsp.com] Sent: Monday, July 20, 2009 10:03 AM To: email@example.com<mailto:firstname.lastname@example.org> Subject: [otlkcon-devel] Status? I'm trying to establish the status of this project - Can anyone tell me which parts of the Exchange SDK are required to build the connector DLL? Has anyone had good results using the connector with Linux servers like Zimbra or Citadel? Thx++ G.
_______________________________________________ otlkcon-devel mailing list email@example.com https://lists.sourceforge.net/lists/listinfo/otlkcon-devel