On Thu, 2008-02-28 at 16:10 +0000, Dafydd Harries wrote: > Ar 28/02/2008 am 06:53, ysgrifennodd harini satyanarayanan:
> Each connection manager can only support those channel types that it has been > programmed to support. Each channel type it supports is mapped to the > underlying protocols. I.e. if the CM supports the Text channel type, it has > code to map that to sending and receiving text messages in the protocols it > supports. So if, for example, telepathy-gabble doesn't support a custom channel type, it wouldn't be possible to just implement a custom channel handler, we'd have to implement our own connection manager? > For applications that need to communicate in ways not supported by other > channel types, we have tubes, which are intended to support general > communication. But in maemo 4.0's case, tubes aren't available in any event (yet). > If you don't have a connection manager that doesn't support tubes, you could > layer your application messages over text channels, but on Maemo, Mission > Control will hand text channels to the chat UI. So what you're saying is that it's simply not possible (on maemo 4.0) to write an app that with a specialized, app-specific communication channel using telepathy. So from what I understand, it looks like the best way to build a maemo app that uses an IM system for app-specific communication today is to use libloudmouth or sofiasip directly and avoid telepathy until the tubes API is available. Would you agree with that? > I hope this clarifies things. > -- Michael R. Head <[EMAIL PROTECTED]> http://www.core.binghamton.edu/~burner/new/resume.html
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Telepathy mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/telepathy
