Quote:
Originally Posted by JayBee  Hello everyone,
I'm a newbie, so pls excuse any silly questions - I'm hoping your collective wisdom will guide me to enlightenment 
I'm looking into having the Zimbra client talk to a different collaboration server.
Having read some of the Zimbra docs I know that the client and server connection is through a well-defined SOAP interface. (Btw, JSON was mentioned also, and I wondered about that..)
So here are my newbie questions:
1) Is there any doc that outlines the set of steps required for re-targeting the Zimbra client to a different server. Such as what code & config needs to be changed and how. If not, what would be a good starting point for me. I've looked into some of the client code but not all of it.. Our server can speak soap / web services and it can be tweaked to match Zimbra client.
2) Curious to know if anyone successfully done this before? If so what was the effort involved? I.e., was it a 2-week project, a 2 month project or a 2 year project ? :-)
Any input will be much appreciated!
Thanks in advance,
- JB |
You can learn what you would need to know just by using firebug to watch the packets, but there really isn't any good reason for this. The backend and frontend are pretty tightly coupled, and sniffing the wire protocol breaks a aweful lot of rules of programming.
Is there any particular reason you would want another backend? Other then you just feel like putting in the 2+ years to duplicate what Zimbra has already done?