Hi,
I've been wanting to set up this sort of 'combined' venue server. How
do I go about choosing a set of multicast addresses that I can use?
since they have to be made as statically assigned addresses, yes?
Derek
Thomas D. Uram wrote:
> The multicast ports are not actually used by the VenueServer
> machine. They are just passed to the clients who actually
> use the ports.
> Bridges for the two versions should be separated between
> two machines, because I haven't seen reliable transmission of
> content between two bridges running on the same machine.
>
> On 2/5/07 12:41 PM, Jeremy Mann wrote:
>> Using this method, the 3.0 server would have to be on a seperate
>> machine because I can't start the 3.0 server with the same Multicast
>> ports used with the 2.4 server.
>>
>> On 2/5/07, Thomas D. Uram <tu...@mcs.anl.gov> wrote:
>>> The solution we have used for this (and NCSA is using) is to mirror
>>> the Venues across the 2.4 and 3.0 servers. 'Mirroring', in this case,
>>> refers only to the Venue names and structure, and audio/video multicast
>>> addresses; shared applications and data can not be shared between 2.4
>>> and 3.0 clients.
>>>
>>> Tom
>>>
>>>
>>> On 2/5/07 12:01 PM, Jeremy Mann wrote:
>>> > Is there currently a way to have 2.4 and 3.0 clients connect to the
>>> > same virtual venue? The Mac users on campus have upgraded their
>>> > machines and they are all the new duo core Intels which means they can
>>> > only install and run the 3.0.x AG client. We still have a majority of
>>> > 2.4 users so telling everybody to upgrade to 3.0.x is pretty much out
>>> > of the question, at least for now.
>>> >
>>>
>>
>>
>
>
--
Derek Piper - dcpi...@indiana.edu - (812) 856 0111
IRI 323, School of Informatics
Indiana University, Bloomington, Indiana
