| Newsgroups |
gmane.network.jabber.user |
| Message-ID |
<[email protected]> |
Thanks for your response Waqas.
Would you happened to have any insight into what was discussed in terms of
roster subset queries or where I may look to find information? I am going to
have to implement this on my own by modifying vysper to allow rosters to be
fed in from backend process and then loaded into the server based on
extending the client Roster request.
So far I can see that if I get past the client / server protocol extensions
I need to:
1. Trigger the presence broadcast to the new roster subset. (I am thinking
that if I just have the client resend current presence after the new roster
is loaded into the server then that should handle it.)
2. Trigger the outbound probes.
Somehow though if it were this simple it probably would have been done
already.
So if you have any more information I would appreciate it.
thanks,
-paul
-----Original Message-----
From: Waqas Hussain
Sent: Wednesday, January 25, 2012 4:16 PM
To: Jabber/XMPP end-user discussion list
Subject: Re: [Juser] XMPP Roster Filtering
On Wed, Jan 25, 2012 at 2:36 AM, <[email protected]> wrote:
> Hello,
>
> I am struggling with a particular usage pattern that would really be
> helped
> if the XMPP spec provided the ability to allow the client to request only
> a
> subset of their roster by groups or eventually a filter query.
>
> The basic idea is that say my roster is comprised of groups A-J and these
> groups relate to particular social groups within the hosting application.
>
> So let’s say I am in group A and I only want to see presence notifications
> from those within group A. As it stands now it seems like I am stuck
> getting
> notifications from groups A-J (The summation of my roster) and just
> ignoring
> all those from groups B-J.
>
> But In this scenario 90% of the server work and generated traffic would be
> wasteful which is what I am trying to avoid.
>
> I realize I am still lacking a mechanism for dynamically changing the
> roster
> view post-login but one thing at a time. So I would appreciate any insight
> or thoughts you may have on this.
>
> thanks,
>
> -paul
>
The only way to do this on an stock XMPP server today is through
XEP-0016: Privacy Lists. Note that while this will decrease client
traffic, it would probably increase server work. XEP-0191: Simple
Communications Blocking probably wont fit your use-case.
Your other option is writing a plugin for the server you are using
(I'm assuming you have control of the server). Given that your
use-case is fairly simple, a plugin shouldn't be too much work.
On the topic of specs, there has been discussion on the XMPP standards
list in the past regarding extending roster functionality in various
ways. This has included roster views (what you want), sub rosters
provided by entities other than the user's server, etc. There are no
specifications yet though.
--
Waqas Hussain
_______________________________________________
This is JUser -- a mailing list for end users
of Jabber/XMPP clients.
To unsubscribe, send email to
[email protected]
or go to the following web
page, scroll all the way down,
and type in your email address:
http://mail.jabber.org/mailman/listinfo/juser
_______________________________________________
_______________________________________________
This is JUser -- a mailing list for end users
of Jabber/XMPP clients.
To unsubscribe, send email to
[email protected]
or go to the following web
page, scroll all the way down,
and type in your email address:
http://mail.jabber.org/mailman/listinfo/juser
_______________________________________________