Luca Bortot wrote:
Charles N Wyble wrote:
Cool. Just wanted to point that out. I apologize if it seems that I am trying to point out your flaws or anything. I just have done my homework in this space and don't want others to miss out. Hmm.... I need to document all this stuff. :)
Indeed, you should definitely! If things go as I'd like, sooner or later I will need to study it, too :-))
Agreed. Your welcome to anything I produce of course.
Well. That is an excellent question. If I was paid to work on it by an enterprising company that wanted to play early adopter I could more then likely have a beta out in the second quarter. I have a wide variety of contacts I have made and that want to help. I simply have not had the time/motivation to organize them and get something shipping. If your organization would like to discuss possible part time employment I would be most interested. I have some managment skills and can take code written by others and understand/modify it fairly well but from scratch coding I am still very new to.
how curious: I'm usually faster on re-writing than on understanding...
HeeeHee. We might make a good pair :)
At this point I cannot say if, as company, we're interested in funding the project in other ways than just my time.
Of course. I understand. Your time is valued as much as financial backing..... if not more so.
Let me better understand the situation before answering :-)
Thank you for your honesty and caution. I appreciate that more then any false hope or promises.
I'm not even sure if the connector approach is the best solution (although I think it is).
Well. I would disagree. A connector requires software to be deployed/maintained on each workstation and that is an expensive (time/money wise) process. I was an admin at a company with ~100 users and developed a custom software deployment system for our network. Using SMS was out of the question because of the expense. And we are still on an Exchange 5.5/NT4 architecture so even if SMS was available the expense of moving to Active Directory and Exchange 2000 or later is a show stopper.
Now, I don't want to force you all on talking about my company requests, but I think we could be a nice case study for "Outlook/Exchange *open* interoperability".
No worries. I am more then happy to work with your company on building a solid case study for other organizations to look at when deciding if the magic that is open exchange/outlook interop works or not. It only takes one forward thinking (brave/foolish? :) ) organization of moderate size and importance to adopt this to make it worthwhile for other organizations.
Yes there will be challenges. Yes there will be delays. This all needs to be documented along with the success. That is the main issue I have with Microsoft case studies. They don't discuss challenges and problems in a candid way at least to my level of comfort. If we document everything and have a solid understanding of where we are where we have been and where we are going, then we will win every single time.
The subject of the thread no longer being adequate for this, I'll start a new one.
Good idea :)
--
Charles N Wyble
Homepage: http://www.thewybles.com/~charles
Blog: http://jackshck.livejournal.com
Developer/Consultant. 30.00 an hour is my fee.
------------------------------------------------------- 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
