Hi, Am Montag, den 09.10.2006, 13:55 +0200 schrieb Thomas Weidner: > Why only focus on the XMPP protocol ?
Because you also focus on the HTTP protocol if you implement an
HTTP-client. It is not worth thinking on supporting Gopher.
> It should be no big problem to define an class/interface which is able to
> handle also other protocols than XMPP.
XMPP != IM-protocol. This is an often told nightmare, which is sad. XMPP
stands for »Extensible Messaging and Presence Protocol«, while Jabber is
the concrete implementation of messaging and presence. We can build a
Zend_Chat or Zend_Im interface for various protocols upon Zend_Xmpp, but
I would not prefer the other way around. I'm a fan of concluding from
the complicated to the simple things. There could be Zend_Im, it could
utilize Zend_Xmpp and is is worth thinking about. But the Jabber
protocol is worth to be supported as complete as possible.
The problem is, that a unification of ICQ, MSN, YIM, GaduGadu, etc. and
Jabber tends to lead to the problem, that all protocols becomes stripped
down to the lowest level (see libgaim and it's derivates). Let's face
the facts, ICQ does not even supports a sensible subscription mechanism,
while Jabber does (subscription "to", "from", "both"). To be fair, ICQ
is a completely different protocoll for a completely different target.
The only intersection of ICQ and Jabber is, that both supports instant
messaging in some ways.
Greets, Lars
--
"Kriterium des Wahren ist nicht seine unmittelbare
Kommunizierbarkeit an jedermann"
-- Theodor Wiesengrund Adorno, aus: »Negative Dialektik«
name: Lars H. Strojny web: http://strojny.net
street: Engelsstraße 23 blog: http://usrportage.de
city: D-51103 Köln mail/jabber: [EMAIL PROTECTED]
f-print: 1FD5 D8EE D996 8E3E 1417 328A 240F 17EB 0263 AC07
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil
