Few things come to mind: * You can get support for other protocols. If your users prefer MSN, you might be able to satisfy them better. * Better integration with other apps. Other apps can also use telepathy/listen on DBUS and perhaps deliver notifications better suited for the user's current DE. * If you are developing a fullscreen app (for example, a game) your users might be happy to have their Telepathy notifications pop up.
Downsides: * If user does not have telepathy, he/she needs to get it and install it for their OS. This may pull other dependencies. I haven't yet tried writing an app either with some XMPP library nor with Telepathy, so take my comments with a grain of salt. On Thu, Feb 18, 2010 at 22:47, Paddy Carman <[email protected]> wrote: > Hi All, > I'm planning to develop an application uses XMPP. I would like to know > the pros and cons of implementing my application using an XMPP library > directly Vs. using Telepathy. I understand that if I use Telepathy I can > later change the underlying XMPP connection manager implementation without > changing my application. But does this benefit come at the cost of losing > some XMPP functionality that I would've been able to use had I integrated my > app. with an XMPP library directly? > > In other words, does Telepathy interface abstraction reduce any of the XMPP > functionality that my app. could make use of (that would be provided by an > XMPP library)? > > Thanks in advance for your expert comments! > Paddy > > _______________________________________________ > telepathy mailing list > [email protected] > http://lists.freedesktop.org/mailman/listinfo/telepathy > > -- Regards, Ivan Vučica
_______________________________________________ telepathy mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/telepathy
