You could write the server-side of the protocol this client expects for instance.
Er, no, don't do that unless you want to keep tracking our ever-expanding knowledge of exactly how Exchange works. OpenGroupware made their server work against Connector 1.2, and then it just failed against Connector 1.4.
Admittedly, if they had had the source, they could have figured out why, and fixed things, but the point is that Connector doesn't really have a real, official, documented "protocol". It just does whatever works best for us at the time, and we're always figuring out new things.
If you're going to try to hack in to one of the Evolution backends, it would be better to use the GroupWise SOAP interface, since that does have well-defined semantics. (Although that API will also be changing over time.)
The best would be to get CAP or CalDAV finalized and out the door so Evolution can support those.
Slashdot Mirror
Er, no, don't do that unless you want to keep tracking our ever-expanding knowledge of exactly how Exchange works. OpenGroupware made their server work against Connector 1.2, and then it just failed against Connector 1.4.
Admittedly, if they had had the source, they could have figured out why, and fixed things, but the point is that Connector doesn't really have a real, official, documented "protocol". It just does whatever works best for us at the time, and we're always figuring out new things.
If you're going to try to hack in to one of the Evolution backends, it would be better to use the GroupWise SOAP interface, since that does have well-defined semantics. (Although that API will also be changing over time.)
The best would be to get CAP or CalDAV finalized and out the door so Evolution can support those.