Re: [otlkcon-devel] Status?
Kervin Pierre schrieb: Another thing that I would like to do is to move the data layer from C++/SQLite to C#/SQL Server Compact ... that would help with getting new developers in the future. You bet on this! If I get a really working sort of bridge between Outlook and a well-defined C# interface in my hands, I will 100% surely add the second step from this interface to whatever my customers use. Native Zarafa is first on my list - hell, just a MySQL database directly on a server would provide excellent opportunities! Sorry for not working on the first part - my C[++] skills are really bad. I implemented a Storage Provider in Pascal, but it never really worked well. Best regards, Eugen -- ___ otlkcon-devel mailing list otlkcon-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/otlkcon-devel
Re: [otlkcon-devel] Status?
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] Sent: Monday, July 20, 2009 10:03 AM To: otlkcon-devel@lists.sourceforge.net 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 otlkcon-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/otlkcon-devel
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] *Sent:* Monday, July 20, 2009 10:03 AM *To:* otlkcon-devel@lists.sourceforge.net *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 otlkcon-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/otlkcon-devel
Re: [otlkcon-devel] Status?
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-0a110307611eDisplayLang=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] Sent: Tuesday, July 21, 2009 5:17 PM To: Kervin Pierre Cc: otlkcon-devel@lists.sourceforge.net 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.commailto:g...@novadsp.com [mailto:g...@novadsp.com] Sent: Monday, July 20, 2009 10:03 AM To: otlkcon-devel@lists.sourceforge.netmailto:otlkcon-devel@lists.sourceforge.net 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 otlkcon-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/otlkcon-devel
Re: [otlkcon-devel] status report
Kervin L. Pierre wrote: [snip] This is just the point I was at when I had to start looking on the calendar protocol ( settled on CalDAV for now ). Part of the problem is that we simply need more hands. I can't help much with calendaring, other than parroting my frustrations in using Thunderbird in an Outlook-centric workplace and dealing with calendaring issues. The provider init method implementation is suppose to detect that previous objects have been initialized, and return that instead. It was not a problem, but I need to start nailing down how the connector will behave on the wire, and what server-side software would be needed, so I switched focus to that. What I've done in the past is have new objects for both the IMSProvider and the IMsgStore objects and let IMsgStore create an interface to a shared back-end object during the Logon call. It occurs to me that it might make more sense to have the IMsgStore object itself be shared. Sometimes tried-and-true template programming isn't such a great idea. ;) It might be a good starting point if you grab CVS and see where we're at. Let me know what you think, Kervin Will do. I'm unclear as to the goal of this portion of the project, though. As I understand it, the goal is to provide an API that exposes all the groupware functionality of Exchange, and the MAPI SP bit just exposes things that are already available...through MAPI. Is that a fair analysis? Brent --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag--drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ otlkcon-devel mailing list otlkcon-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/otlkcon-devel