[standards-jig] calendaring?

Julian Missig julian at jabber.org
Thu Mar 14 01:51:50 UTC 2002


On Wed, 2002-03-13 at 19:16, Dave wrote:
> Reply inline:
> 
>  - Dave
> 
> Julian Missig wrote:
> > 
> > On Wed, 2002-03-13 at 18:40, Dave wrote:
> > > Reply inline:
> > > 
> > > Julian Missig wrote: > > The current routing method. I was just proposing
> > > using browse for very > basic routing. If resource x is the only resource
> > > which support > jabber:iq:negiotiate:video, then it shouldn't be sent
> > > to resource y.  ...but the current routing method is rather severely
> > > limited in its ability to accomodate multiple simultaneous resources :-(
> > > 
> > > > > Also, in your previous message what you you mean by "Furthermore, >
> > > "enhancing" the browse method to support clients would probably create
> > > a > large argument later"? My proposal would require no changes to the
> > > > browse protocol, it's just an augmentation of the current routing >
> > > method.  I said "enhancing" because I knew that saying enhancing (with
> > > no quotes) would trigger an argument.  The end result is that you're
> > > expanding the browsing protocol to include servers browsing clients,
> > > and making routing decisions based on the results.  Let's not bicker
> > > about wording ;-)
> > 
> > Howso? There's nothing preventing a server or server component from
> > browsing a client right now. The browse JEP makes no restrictions
> > against it.
> ...but the routing spec says that the server shouldn't use the result of
> a client browse to affect routing, so what use is browsing the client???

So we change the routing spec :)

-- 
email: julian at jabber.org
jabber:julian at jabber.org




More information about the Standards mailing list