For the quickest reply, please use our new Customer Helpdesk and Feedback platform
 
   
 
exmpp improvements
Posted: 05 June 2009 12:55 PM   [ Ignore ]
Newbie
Avatar
Rank
Total Posts:  2
Joined  2009-06-05

As exmpp is still work in progress, I guess such a thread is necessary ;)

First thing :
I’m writing some code to connect to a MUC.

The #received_packet{} record is great, but it could be a bit better!

Case in point : the from field. It just holds a string. I’d pretty much rather it to return the jlib:jid_to_lower term :
{Node, Server, Resource}, because ... pattern matching :)

If I am to write a MUC client, I’d like to pattern match on {“room”, “conference.localhost”, Sender} in my receive loop.

That would imply implementing the exmpp_jid:make({Node, Server, Resource}) and the exmpp_jid:to_lower(JID)

This JID representation is so useful in ejabberd (see mod_muc, mod_pubsub) I’d love to have here too.

And while I am at it, I’d like to have several client_pids subscribing to events by pattern matching this same #received_packet{} on sender or query_ns. Of course, I might end up doing it myself, but that would be very nice to have as an option.

Profile
 
 
Posted: 08 June 2009 01:47 PM   [ Ignore ]   [ # 1 ]
Administrator
Avatar
RankRankRankRank
Total Posts:  600
Joined  2006-11-12

Good idea, thank you !

I have created a ticket for that in the new development ticket tracker: https://support.process-one.net/secure/BrowseProject.jspa

Profile
 
 
Posted: 01 February 2010 03:56 PM   [ Ignore ]   [ # 2 ]
Newbie
Rank
Total Posts:  1
Joined  2010-02-01
Mickaël Rémond - 08 June 2009 01:47 PM

Good idea, thank you !

I have created a ticket for that in the new development ticket tracker: https://support.process-one.net/secure/BrowseProject.jspa

Such a very amazing link!
Thanks you for the post.

Profile