[jadmin] Access to Openfire IM gateway plugins

[Daniel Henninger]

That is indeed bizarre because the IM Gateway plugin has never supported external users.  I'll give you a little background as to why.  =)  One of the biggest problems I had when I wrote PyAIM-t and PyICQ-t was when rosters got out of sync.  Your XMPP roster could reflect one list of users and your AIM roster might be slightly different.  There was no direct way for the transport to "set" your roster and make sure it's got the right list of users in it.  And due to this lack of direct control, new end users who joined the AIM transport would get hella flooded with "Do you want to accept this person in your roster?".  Very user unfriendly. With the IM Gateway plugin built directly into Openfire, I was able to user internal APIs to put roster items directly into ones roster.  As a result however, the users -must- be on the same server as the transport or there's no way to use the internal APIs.

PyAIM-t and PyICQ-t and just about every other transport on the face of the planet supports external users using it.  I think the IM Gateway plugin is alone on that front.

As for supporting remote users, I have no idea if I'll ever end up adding that honestly.  I don't want to compromise the end user's experience so it would require some serious XEP work I think.  ;)  Something which I do not have time to do.

Daniel

On 5/21/08 3:52 AM, "Tobias Klausmann" <klausman-jabber at schwarzvogel.de> wrote:

Hi!

On Tue, 20 May 2008, Jeff Garner wrote:

> Can you give the names of the transports that you are using?  are they
> the Py<..> transports or the gateway plugins inside of Openfire?

The latter. Specifically the ICQ portion. It works dandy for me
and other local users, remote users get either nothing at all or
a "Permission denied" style error message.

Daniels statement regarding the GW plugins:
Daniel Henninger wrote:
>  I'm assuming you are not referring to the IM Gateway plugin,
>  which +does not work for external users at all.

This makes me wonder why it worked before (or why it took
external users several weeks to notice it didn't). Also, are
there any plans to make it work form outside. Near as I can tell,
the GW plugin looks just like an external transport (like pyicq-t
which I used earlier) to my client.

> I have recently upgraded from 3.0 to 3.3.3 and then to 3.5.1,
> updated my plugins and everything is working fine.  Please more
> information.

I will try to reproduce it, possibly with XML dump, tonight.

As for the question in the earlier reply by Daniel Henninger: I
wouldn't know why the openfire devs might decide to remove remote
access, but that doesn't mean there can't be good reasons for it
;)

Regards,
Tobias


--
printk("NULL POINTER IDIOT\n");
        linux-2.6.6/drivers/media/dvb/dvb-core/dvb_filter.c
_______________________________________________
JAdmin mailing list
JAdmin at jabber.org
http://mail.jabber.org/mailman/listinfo/jadmin
FAQ: http://www.jabber.org/discussion-lists/jadmin-faq
_______________________________________________

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.jabber.org/pipermail/jadmin/attachments/20080521/f0f62b97/attachment.htm