[AG-TECH] Idea for creating "observer only" venues

Ivan R. Judson judson at mcs.anl.gov
Sun Oct 24 20:07:27 CDT 2004

Hey Frank,

In one respect I agree, the details are not completely implemented, in
another I disagree, since it's entirely conceivable that a client can call
the "enter" operation on the venue, but not the "negotiate_capabilities"
call which would give them stream information.

We're currently considering how to support these calls in the next release
and the ideas we have might support exactly what you're pointing out as a
use case. We'll have to make sure.

In any case, if the venue can provide this functionality, it's much easier


> -----Original Message-----
> From: Frank Sweetser [mailto:fs at WPI.EDU] 
> Sent: Sunday, October 24, 2004 3:55 PM
> To: Ivan R. Judson
> Cc: 'Frank Sweetser'; ag-tech at mcs.anl.gov
> Subject: Re: [AG-TECH] Idea for creating "observer only" venues
> On Fri, Oct 22, 2004 at 08:20:36PM -0500, Ivan R. Judson wrote:
> > 
> > 
> > Seems like just using some authorization facility would be easier. 
> > Just don't allow those participants to "write" to the venue.
> > 
> > The authorization stuff that's in 2.X is admittedly 
> incomplete and the 
> > SOAP latency makes it hard to use, but it's proven itself when it 
> > comes to the design and structure. In 3.X we'll have to 
> make sure it's 
> > fast enough to be usable because with it you could do what I'm 
> > describing, which is what you really want. you don't really want to 
> > bridge venues this way, it's plumbing at the wrong level of 
> the system, IMHO.
> In principle I agree with you.  However, the problem I see is 
> handling the media streams.  If a person is allowed into a 
> given venue, there's currently no way to forcibly make their 
> rat (for example) recieve only, and completely disable the 
> talk option.  Since the actual media data doesn't go through 
> the venue server, there's really currently no way to enforce 
> read only vs read write with respect to video or audio.
> --
> Frank Sweetser fs at wpi.edu
> WPI Network Engineer
> GPG fingerprint = 6174 1257 129E 0D21 D8D4  E8A3 8E39 29E3 E2E8 8CEC

More information about the ag-tech mailing list