Good luck with that... I tried this with a media server team a few years back and we found that most providers block multicast. We were able to multicast streams only on our corporate and development networks, once it hit Quest, COX, or AT&T the packets disappeared. :(
Paul On 2/22/07, joseph wamicha <[EMAIL PROTECTED]> wrote:
Hi, Storm: No problem. I can't think of another way to limit the bandwidth though; I wonder if there is another way too... Dan: I'd probably keep a list of servers; a server for each region, just like the way we have download mirrors for different regions. Clients in one region connect to the server in their region (so that would take care of load balancing). However, the main red5 server with the live stream, writes the stream to all the servers in all the regions. >Cam--->red5 ---> red5 ----> The world @joseph: if i'm catching your idea what you want to do is: and in the last step you'd have the same bandwidth issue. Sending streams from one red5 to other is an interesting concept itself nontheless, but sadly i'm into a corporative network without exit to the world so i won't be able to do that kind of test atm, sorry. @Dan: i'm not really looking for that kind of "geo-balance", in fact all the connections would be from the same region in Spain, we just need to retard the bandwidth usage explosion as much as possible. Keep sending your ideas, we might come to some kind of solution useful for many types of apps! Cheers Carlos -- C is forever. _______________________________________________ Red5 mailing list [email protected] http://osflash.org/mailman/listinfo/red5_osflash.org
-- The early bird may get the worm, but the second mouse gets the cheese.
_______________________________________________ Red5 mailing list [email protected] http://osflash.org/mailman/listinfo/red5_osflash.org
