[JDEV] Promiscuous presence for user communities (with patch)

[Henk Spaay]

My 2c's, another approach...

Create a 'group-JID'. You then subscribe to presence of the group JID just
like you would to presence of another user. 
All presence, IQ, and messaging messages sent to the group JID is fanned out
to all subscribers. This needs a module on the server to handle the fan-out
and membership access control.

The nice thing of this method is that you don't need to know in advance who
the group members are, but you can still reach them.

The problem to solve is how you create a group JID within the existing
protocol. Maybe another namespace while creating the group account? 

Cheers,
Henk



> -----Original Message-----
> From: Peter Saint-Andre [mailto:stpeter at jabber.org]
> Sent: Wednesday, October 01, 2003 11:31
> To: jdev at jabber.org
> Subject: Re: [JDEV] Promiscuous presence for user communities (with
> patch)
> 
> 
> Naturally it would help if I finally got around to writing a developer
> guide! So I certainly don't blame Steven. Preparations are 
> under way for
> working on more documentation.
> 
> Peter
> 
> On Wed, Oct 01, 2003 at 05:19:43PM +0100, Richard Dobson wrote:
> > > As to making changes to the Jabber protocol, I don't 
> understand all the
> > > concern. I agree that it is always best to try to work 
> within a protocol,
> > > but I thought that part of the point of open source 
> software is that you
> > > could modify it "willy nilly" to meet your own needs. 
> Generally not
> > advised,
> > > but sometimes the only option. I don't think that Steven 
> posted this as a
> > > protocol change, but simply as a solution to this problem 
> for other people
> > > like myself trying to do the same thing.
> > 
> > The point I think he was trying to make was that some of 
> the suggested best
> > solutions were infact potensially dangerous to the rest of 
> the community
> > because they broke the existing protocol rather than using 
> extablished
> > methods of extension that would not have been any real problem.
> > 
> > e.g.
> > 
> > <presence type="promiscuous"/>
> > 
> > This breaks existing protocol and could cause problems if 
> they come into
> > contact with existing or future compliant implementations.
> > 
> > <presence>
> >     <promiscuous xmlns="http://yourwebsite.com/jabber/promiscuous"/>
> > </presence>
> > 
> > Whereas this uses the standard method of protocol extension 
> and should not
> > cause any problems when coming into contact with standard compliant
> > implementations.
> > 
> > I think that the main problem is the seeming lack of caring 
> and "willy
> > nilly" approach that was used with creating the 
> modification, which could
> > cause problems for the greater Jabber community as a whole. 
> If you work with
> > us not against us I doubt you will have any problems and 
> more importantly
> > not cause the rest of us problems that we have to then clean up.
> > 
> > Richard
> > 
> > _______________________________________________
> > jdev mailing list
> > jdev at jabber.org
> > http://mailman.jabber.org/listinfo/jdev
> 
> -- 
> Peter Saint-Andre
> Jabber Software Foundation
> http://www.jabber.org/people/stpeter.php
> 
> _______________________________________________
> jdev mailing list
> jdev at jabber.org
> http://mailman.jabber.org/listinfo/jdev
>