Fwd: EQO messenger

[Phil Hannent]

Ethan Blanton wrote:
> Second, as that discussion also included, it depends on what the
> daemon/service *looks* like.  If the service is just a remote
> procedure-style API (as the D-Bus service for Skype is, or the
> libpurple D-Bus service), it would fall under this clause.  If,
> however, it is an IM-like protocol or other more abstract protocol
> behind which libpurple does a translation to the protocols spoken by
> the various IM networks, then it would be OK.  As an example, think
> about Jabber transports; these are quite clearly a translation of one
> abstract IM protocol to another abstract IM protocol, and not a remote
> API for a particular IM protocol implementation.
Thank you for taking the time to reply, that is most helpful.

Regards
Phil Hannent

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 187 bytes
Desc: OpenPGP digital signature
URL: <http://pidgin.im/pipermail/devel/attachments/20080131/3e87c08f/attachment.sig>