[Icecast] Use of TCP_CORK instead of TCP_NODELAY
daleg at elemental.org
Mon Dec 26 16:31:14 UTC 2005
Make sure your patch accounts for the fact that not all platforms
On Dec 25, 2005, at 9:04 AM, Henri Zikken wrote:
> We're abusing icecast in a true narrowcasting setup (personalized
> stream per
> mountpoint). The streams itself are created in a piece of proprietory
> (spelling?, i'm dutch) software, icecast merely relays them.
> However, the intended endpoint is an embedded device. This device has
> trouble with tcp/ip packets not matching the max. packet size (MSS
> or MSS
> minus header). After eleborate testing, we found that using the
> 'TCP_CORK' instead of 'TCP_NODELAY' produces far better results on
> the field
> on reconnects etc/. Also, with streaming media, TCP_CORK is more
> than TCP_NODELAY.
> To patch icecast to use tcp_cork is a piece of cake, it involves no
> than 10 lines of code. My question would be if the maintainers would
> consider bringing this into the main tree. It could be implemented
> as flag
> for configure, of, (even better) as some setting in the config file.
> I have already implemented this as configure flag. If this is
> something usefull, i will submit the patch i created.
> Henri Zikken
> Icecast mailing list
> Icecast at xiph.org
More information about the Icecast