Received-SPF: none
 receiver=mail.stalker.com; client-ip=212.74.130.193; envelope-from=fmarchand@debiopharm.com
Subject: RE: Calendar update loop with iPhone is back
Date: Fri, 26 Jun 2009 09:24:37 +0200
Organization: Debiopharm S.A.
Message-Id: <65eeca636f55ef4496ffba91602a9110@mail.lnn.debiopharm.com>
In-Reply-To: <list-54219379@mail.stalker.com>
MIME-Version: 1.0
Thread-Topic: Calendar update loop with iPhone is back
Priority: Normal
Importance: normal
Sensitivity: Normal
Thread-Index: Acn2LykXm7/BBj99Ql+hR7cESoCabg==
From: =?iso-8859-1?B?RnLpZOlyaWMgTWFyY2hhbmQ=?= <fmarchand@debiopharm.com>
To: "CommuniGate Pro Discussions" <CGatePro@mail.stalker.com>
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

And what about recursive events support? If you change an occurrence of a r=
ecursive event, it disappear from freebusy, pronto, webmail... Instead of i=
mplementing load of new features, they should try to complete and fix exist=
ing ones.

Fred

-----Message d'origine-----
De=A0: CommuniGate Pro Discussions [mailto:CGatePro@mail.stalker.com] De la=
 part de birnenschnitzel@volloeko.de
Envoy=E9=A0: vendredi, 26. juin 2009 07:13
=C0=A0: CommuniGate Pro Discussions
Objet=A0: Re: Calendar update loop with iPhone is back

Same here,

we always have been happy Communigate customers but still on the 5.1 releas=
e. Since a year we want to upgrade to provide our users AIRSYNC support. Ev=
ery 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 cal=
endar items are duplicated or meeting requests are resent. This is not for =
productive use. Better to not provide AIRSYNC than to provide a faulty impl=
ementation.

Although this is the top feature our users request I won't open support req=
uest. 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 abo=
ut AIRSYNC. If the following topics had top priority at Communigate they wo=
uld 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 pl=
atform (as it is advertised). I could not believe how tricky this could be.=
 Switching for tests from ejabberd to communigate revealed errors that we h=
ad 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 hav=
e substantial external effects. The user gets the experience: I tell the ad=
min 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 anyo=
ne.

Best regards
-- 
GRATIS f=FCr 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>