[JDEV] Info/Query && filter proposals..
scott at tranzoa.com
Wed Aug 18 19:45:31 CDT 1999
* Anders Qvist translated into ASCII [Wed, Aug 18, 1999 at 12:07:38PM +0200][<Pine.LNX.3.96.990818104847.26059W-100000 at valdez.netg.se>]
> New revision of Jabber filter proposal. Grab at:
> > > This would also allow for public inheritable
> > > filters across entire systems, such as querying
> > > for the filter info from a <Target>SERVER</Target>.
> > >
> > I didn't see anything in the current implementation that didn't allow for
> > inheritable filters. In fact, I assumed they would be implmented.
> Filter inheritance? Yes, a good idea ... hm ... problem is you can't
> really inherit a hierarchical structure. What would it mean to inherit
> another set of filters? Does it mean that the inherited filters should be
> placed at some point inside the current filters or does it mean that the
> current filter should be enclosed in the inherited filters?
Perhaps inheritance is a misnomer. What I envisioned was just processing the
server's filters before processing the user's filters.
> I added a proposal for an include mechanism with namespaces instead. Have
> a look at 7.1 in the revised proposal. I think this is easier. If we want
> to add global filters to apply to all users/sessions/whatevers, we apply
> them before user filter get to say anything - no need for inheritance
I'll take a look.
> > > Oh, and Anders Qvist, when saying this:
> > >
> > > <filter messagesize="1000k"></filter>
> > >
> > > you can more easily, and breif:
> > >
> > > <filter messagesize="1000k"/>
> I don't see what this will gain us (except making filter descriptions a
> few bytes shorter). It will increase interpretation complexity slightly.
Not really more complex. Everyone else does it that way anyway.
More information about the JDev