|
|
And what about recursive events support? If you change an occurrence of a recursive event, it disappear from freebusy, pronto, webmail... Instead of implementing load of new features, they should try to complete and fix existing ones.
Fred
-----Message d'origine-----
De : CommuniGate Pro Discussions [mailto:CGatePro@mail.stalker.com] De la part de birnenschnitzel@volloeko.de
Envoyé : vendredi, 26. juin 2009 07:13
À : CommuniGate Pro Discussions
Objet : Re: Calendar update loop with iPhone is back
Same here,
we always have been happy Communigate customers but still on the 5.1 release. Since a year we want to upgrade to provide our users AIRSYNC support. Every new 5.2 version is installed on our testserver and we play around with this interface. In less than a week we find at least one situation when calendar items are duplicated or meeting requests are resent. This is not for productive use. Better to not provide AIRSYNC than to provide a faulty implementation.
Although this is the top feature our users request I won't open support request. You may ask why. I'm simply tired of the progress of the AIRSYNC and the MAPI implementation. MAPI seems to be always neglected when talking about AIRSYNC. If the following topics had top priority at Communigate they would have been fixed much faster:
- Calendar duplicates using AIRSYNC
- Meeting invitations sent multiple times
- IPhone Calendar update loop
- MAPI is not able to support birthdays before 1970/1/1 in VCARDs
- Intransparent or missing mapping of Outlook fields to VCARDs
Besides that we tried to use Communigate as our unified jabber messaging platform (as it is advertised). I could not believe how tricky this could be. Switching for tests from ejabberd to communigate revealed errors that we had never seen before:
- inconsequent use of resource flag in XMPP requests
- rudimentary XMPP protocol extensions implemented
- difficult to find jabber clients that work with Communigate
For the administrator these bugs are extremly difficult to handle. There is no script or tool he can write to intercept the protocols and to fix these errors temporary. So his hands are bound. On the other hand these bugs have substantial external effects. The user gets the experience: I tell the admin about a bug but nothing happens. Last but not least the admin gets the experience: I tell Communigate about the bug and nothing happens.
To sum it all up as others wrote: Communigate should tell users about their priorization of errors like these. The cloak of secrecy does not help anyone.
Best regards
--
GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT!
Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01
#############################################################
This message is sent to you because you are subscribed to
the mailing list <CGatePro@mail.stalker.com>.
To unsubscribe, E-mail to: <CGatePro-off@mail.stalker.com>
To switch to the DIGEST mode, E-mail to <CGatePro-digest@mail.stalker.com>
To switch to the INDEX mode, E-mail to <CGatePro-index@mail.stalker.com>
Send administrative queries to <CGatePro-request@mail.stalker.com>
|
|