search for: refbuf_t

Hello, I work at SmarctJog.com, we have here some patches on IceCast for performance and reliability, these are mostly client/connection/source cleanups (a slave merge is underway, and some more good stuff (c)), but we'd like this to be merged in before the list gets any longer. Please find attached a list of our patches with a short desc: This one is actually not from us/me, it was found

> you can't keep them in the main queue because you are subject to the > queue size cutoff so you either keep this within the per codec handle > structure (codec list) and/or in the block for the header pages (via the > associated pointer). The sending handlers are not really codec aware > but they do notice a change in headers. Yes, but that's the problem I'm facing:

...s just one and you can have codec specific allocations of those flags. Also the check_buffer routine is called before the send_to_listener. It's used to populate data from intro/fallback files or progress through the queue. You could set a special check buffer handler that checks the above refbuf_t flags. It's possible to create a per-client refbuf_t within there that hooks back into the queue. karl.

...src->dumpfilename = strdup (mountinfo->dumpfile); + if (mountinfo->max_listener_time != NULL) + src->max_listener_time = mountinfo->max_listener_time; } if(src->dumpfilename != NULL) { *************** *** 191,196 **** --- 194,200 ---- refbuf_t *refbuf, *abuf; int data_done; + int client_connect_time; int listeners = 0; #ifdef USE_YP *************** *** 202,207 **** --- 206,214 ---- #endif long queue_limit; + int global_listener_time_limit; + int mount_listener_time_limit; + int listener_time_li...

...nge: move the logic of actually sending the buffers to another function, and also exploit it to do some flow control. It is working in my site since a year without a glitch. It's something like (for old icecast version): <p>+int send_client_queue(client_t *client, int maxlag) +{ + refbuf_t *abuf; + long bytes, sbytes; + time_t now = time(NULL); + + if (client->last_sent < (now - maxlag * 2)) { + client->con->error = 1; /* lame client or DoS */ + return 1; + } + abuf = refbuf_queue_remove(&client->queue); + while (abuf) { + if (client...

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