Date: Mon, 25 May 2009 23:46:21 +0200 From: cpghost <farid@hajji.name> To: Wojciech Puchar <wojtek@wojtek.tensor.gdynia.pl> Cc: FreeBSD Questions <freebsd-questions@freebsd.org> Subject: Re: Streaming server Message-ID: <20090525214621.GB12424@phenom.cordula.ws> In-Reply-To: <20090525210657.GA12424@phenom.cordula.ws> References: <4A1A9FF0.40609@webrz.net> <4ad871310905251225y6da0f41bl7718e9a3290dfa19@mail.gmail.com> <alpine.BSF.2.00.0905252128380.41119@wojtek.tensor.gdynia.pl> <20090525210657.GA12424@phenom.cordula.ws>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, May 25, 2009 at 11:06:57PM +0200, cpghost wrote: > On Mon, May 25, 2009 at 09:30:30PM +0200, Wojciech Puchar wrote: > > > > > > make search key="streaming" > > > > > > in the ports directory. IMHO, streaming versus downloading is more > > > bandwidth intensive overall. > > > > and give NO adventages. > > > > anyway - file that is available through FTP/HTTP or similar way you can > > stream too. just without any extra tools both under windoze and unix. > > You're aware of UDP-based real-time streaming protocols, right? > RTP being one of them: > http://tools.ietf.org/html/rfc3550 > > In streaming vs. file download there's a trade off. In file streaming, ^^^^^^^^^^^^^^^ Sorry, mistake: s/file streaming/file download/ > all data must arrive, and it doesn't matter that retransmission of lost > packets temporarily interrupts the transmission (that's what TCP does > very well). In streaming, lost packets are tolerated, as long as the > transmission doesn't "hang" (e.g. due to retransmissions). Here, UDP- > based protocols are often a better choice. The point here is that you need special servers and clients for streaming, that are not based on plain old TCP. -cpghost. -- Cordula's Web. http://www.cordula.ws/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090525214621.GB12424>