search for: christioph

> > p.s. For an in depth analysis of TCP_CORK read Christiopher Baus' excelent > article: http://www.baus.net/on-tcp_cork Thanks for this pointer. I'd been meaning to reply on this thread, but hadn't got around to it, primarily because I didn't really understand TCP_CORK (the linux manpage is, as usual, fairly unclear on what exactly it do...

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,

...ine") ps$lty <- 1:7 trellis.par.set("superpose.line",spl) xyplot(a~b|factor+treatment, groups=external,data=ownframe,layout=c(2,2), panel=function(x,y,subscripts,...){panel.superpose(x,y,subscripts,...);panel.lmline(x,y)}) Thank you very much for your help! Regards Christioph

...However, if I understand correctly your TCP_CORK solution would apply to all formats since it is applied on the client socket (irrespective of the format). I would be very interested in having this patch and seeing it applied to Icecast. Cheers, KJ p.s. For an in depth analysis of TCP_CORK read Christiopher Baus' excelent article: http://www.baus.net/on-tcp_cork -----Oorspronkelijk bericht----- Van: icecast-bounces@xiph.org [mailto:icecast-bounces@xiph.org]Namens Henri Zikken Verzonden: zondag 25 december 2005 15:05 Aan: icecast@xiph.org Onderwerp: [Icecast] Use of TCP_CORK instead of TCP_NODEL...

...mail.com [mailto:mlrsmith@gmail.com]Namens Michael Smith Verzonden: woensdag 28 december 2005 17:14 Aan: Klaas Jan Wierenga CC: henri.zikken@deltasolutions.nl; icecast@xiph.org Onderwerp: Re: [Icecast] Use of TCP_CORK instead of TCP_NODELAY > > p.s. For an in depth analysis of TCP_CORK read Christiopher Baus' excelent > article: http://www.baus.net/on-tcp_cork Thanks for this pointer. I'd been meaning to reply on this thread, but hadn't got around to it, primarily because I didn't really understand TCP_CORK (the linux manpage is, as usual, fairly unclear on what exactly it do...