Displaying 4 results from an estimated 4 matches for "use_udp".
Did you mean:
use_ad
2004 Aug 06
2
bug report w.r.t. streaming of metadata in icecast
...d 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 meaningless. therefore, does any use of udpseqnr
within a client_t structure need to be conditioned with use_udp ?
in...
2004 Aug 06
0
bug report w.r.t. streaming of metadata in icecast
...sending 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.
> if the client is connecting with tcp, then i assume that the comparision of
> udp sequence numbers is meanin...
2004 Aug 06
2
bug report w.r.t. streaming of metadata in icecast
...s 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.
could you provide some more info on what client_t.use_udp and
client_t.udpseqnr are for, if not UDP s...
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