Hi,

I've just tested DXMPP and it works fine (except the ordinary DEV-State bugs).
There's just one thing I'm discrepant with, why do you mix up the "Drupal XMPP Communication" and the "Javascript Chat" in one Module?

In my opinion the interface between Drupal and the Jabber-Server should be a single Module so I can easily build other Modules on top!
Doing it all in one Module makes me nearly addicted to one solution like the XMPP Framework!

If you agree to this I'ld love to build the "DXMPP API" Module!

sunny regards

sven rissmann

P.S. Think about Modules like "silent syncing Profilefields <-> VCard"

Comments

aaron’s picture

aaron CreditAttribution: aaron commented

I agree entirely! There's currently a GSOC project to bring this vision to fruition, but you're more than welcome to join on board!

svenrissmann’s picture

svenrissmann CreditAttribution: svenrissmann commented

Hi aaron,

glad to see that my proposal has been accepted ;)
I've just mailed it to darklrd.

Just let me say a few words about what I actually want to do (copied out of the Mail):

What I mean with an API is to have a single Module which handles the Drupal<->Jabberserver Communication.
I think it should present a set of actions like: register, roster_add, vcard_get, and so on.
Doing it so there could be many plugins for the different Servers (Openfire, eJabberd, Tigase, ...)
For example the action "register" could add a user by xml-rpc for eJabberd and SQL-Insert for Tigase!

Just imagine the "DXMPP IM" could use a Server via BOSH no matter if the Drupal-Module for Rostersyncing is UR or Friendlist

...

P.S. If my proposal gets accepted the name of the API Module practically should be DXMPP :-p