search for: clicon

Displaying 4 results from an estimated 4 matches for "clicon".

2004 Aug 06
2
bug report w.r.t. streaming of metadata in icecast
...the data stream. the behavior that i was seeing was that the information was appearing a maximum of one time and sometimes zero times. i believe there is a bug in the following line in write_chunk_with_metadata() in source.c. here is the original: if (source->info.udpseqnr == clicon->food.client->udpseqnr) { and here is the change: if (clicon->food.client->use_udp && source->info.udpseqnr == clicon->food.client->udpseqnr) { if the client is connecting with tcp, then i assume that the comparision of udp sequence numbers is meaning...
2004 Aug 06
2
bug report w.r.t. streaming of metadata in icecast
On Tue, 7 Aug 2001, Brendan Cully wrote: > On Tuesday, 07 August 2001 at 12:56, Richard Fromm wrote: > > i believe there is a bug in the following line in write_chunk_with_metadata() > > in source.c. here is the original: > > > > if (source->info.udpseqnr == clicon->food.client->udpseqnr) { > > > > and here is the change: > > > > if (clicon->food.client->use_udp && source->info.udpseqnr == clicon->food.client->udpseqnr) { > > It's not a bug, the variable is just badly named. I know because I...
2004 Aug 06
0
bug report w.r.t. streaming of metadata in icecast
...quot;updinfo" command. Otherwise the information hasn't changed and there is no point in wasting bandwidth resending it. > i believe there is a bug in the following line in write_chunk_with_metadata() > in source.c. here is the original: > > if (source->info.udpseqnr == clicon->food.client->udpseqnr) { > > and here is the change: > > if (clicon->food.client->use_udp && source->info.udpseqnr == clicon->food.client->udpseqnr) { It's not a bug, the variable is just badly named. I know because I made the same mistake at first...
2004 Aug 06
5
Missing headers in Icecast2
Hi Karl, Thanks for your help, About the "Connection:" header, you are right, it's: "Connection: close" and NOT "Connection: keep-alive". The protocol when the SERVER sends the data is http 1.0. It's http 1.1 when the browser requests the data. I don't understand the "Content-Length: 54000000" header either. Also I noticed the flash player on