In some email I received from Dan Kuykendall <[EMAIL PROTECTED]> on Mon, 07 Jul 2003 11:33:46 -0700, wrote:
I've worked on an exchange replacement some time ago, but it didnt go much further too little interest. And since MSRPC (i think we had a discussion about it here, some time ago) was pain in the ass and no one could be bothered to strip samba and take the RPC code from there and then to reverse engineered some more stuff from windows to make it more native, we decided to stick a code which was supposed to control various stuff within Outlook. there were few important priorities: 1) Compat with Outlook 100% 2) Shared folders, calendar and so. (more granulated per message sharing) 3) File sharing. 4) More ACLs on the server. Everything was performed on the client basically ie Outlook. With a few COM+ addons Outlook can be easily controlled, so that's what we did, wrote some VB code and COM+ stuff, inserted in it, altered the database scheme itself adding a relations with a few more tables. Data was pushed and pulled using this COM+ thingy, also we created a calendar + other storage stuff which were stored encoded in the database. I cant remember how we manage to workaround the calendar implementation in Outlook (have to look at the project again). But basically we lost the speed of LDAP, since SQL was used for all read/write, where LDAP is something like 6times faster in reads. but that wasnt all.. anyway, I'dnt be too interested in PHP since with my experience as a Security Analyst, php was the least thing I would write code in, considering how vuln it is by default. See Java (and now .NET) are different things. anyway just my two bits. cheers > Aaron Stone wrote: > > > Nice to meet you! I've spent 4+ years working with TWIG, which is really > > one of the best web based groupware solutions around ;-) > > heh. yeah, TWIG isnt so bad :-p > > At the moment, I don't feel that DBMail should try to become Exchange in > > all of its intricacies. It's enough to be the first open source project to > > seriously provide for email in a database. Adding a SOAP interface is an > > interesting idea, however. What you're basically saying is that the paths > > taken by phpGroupWare, Horde and TWIG can all be joined back together. > > exactly > > > Rather than each of us defining our own databases for Contacts, Scheduling > > and so on, we could all share a single SOAP specification for which DBMail > > is the backend. Very interesting indeed! > > you understand the idea exactly. > > Now for the hard part of actually getting a SOAP spec designed that > everyone would like and accept.
