Support XMPP URI query types (JEP-0147)

[beerfan]

Websites are starting to use URIs which link to xmpp resources. Other applications also have a need to send a query to Gajim using an XMPP URI. Gajim should probably add support for the standard XMPP URI queries as detailed at the URL below.

http://www.jabber.org/registrar/querytypes.html

These URI queries would look like

xmpp:room@conference.jabber.org?join
xmpp:pubsub.shakespeare.lit?pubsub;action=subscribe;node=princely_musings

[asterix]

see http://www.jabber.org/jeps/jep-0147.html and

http://www.jabber.org/registrar/querytypes.html

[Liorithiel]

Official RFC: http://www.ietf.org/rfc/rfc4622.txt

[misc]

Here is a preliminary patch, that add two things :

• a join_room command, that simply join a room
• a handle_uri command, that take a uri and try to do the right thing ( ie, for the moment, join the room if there is ?join, or open a chat dialog ).

I plan to add more, but as smaller patch are easier to review, test ( and to write ), I try to keep this one as simple as possible.

What do you think about it ?

[misc]

Add preliminary of the xmpp uri support

[asterix]

(In [7748]) [misc] handle uri like room_jid?join. see #2133

[asterix]

it's in. I justmodified it a bit to not have room_jid initialized to room_jid?join in join room dialog.

[baggend]

I've added a new module for handling XMPP URI's as defined in RFC 4622, xmppuri.py. I've also modified gajim-remote.py to use this module for the handle_uri function, as well as a minor fix to the argv length checking that was conflicting with how some URI's were being handled.

Currently supported methods for handle_uri are join, message (with body and subject support), roster, remove, and vcard.

xmppuri currently only implements about 30% of the the RFC spec. I will be adding more functionality as I have time. Most of it won't be directly applicable to the code in gajim-remote, but there's currently no RFC 4622 Python library out there so it needs to get done.

[baggend]

A few more bug fixes and added support for the 'type' key for the message querytype. Looking more at this code, I think this is the wrong way to be implementing this. I think moving forward the dbus handler should do the URI handling, not the gajim-remote frontend. This way other applications that talk to gajim over dbus could send URI's directly.

[steve-e]

Sorry, no time.