search for: sock_set_blocking

....%d.%d.%d", &lsb, &b2, &b3, &msb) < 4) { return 0; } #ifdef HAVE_INET_ADDR a->s_addr = inet_addr(s); if(a->s_addr == -1) return 0; #else a->s_addr = lsb + (b2 << 8) + (b3 << 16) + (msb << 24); #endif return 1; } #endif /* _WIN32 */ int sock_set_blocking(SOCKET sockfd, const int block) { #ifdef _WIN32 int varblock = block; #endif if ((!sock_valid_socket(sockfd)) || (block < 0) || (block > 1)) return SOCKET_ERROR; #ifdef _WIN32 return ioctlsocket(sockfd, FIONBIO, &varblock); #else return fcntl(sockfd, F_SETFL, (block == SOCK_BLOCK)...

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

...ike in the function stats_event_inc. Can this be improved or > > is there anything we didn't understood or saw ? > > > > ---------------------------------------- > > > > In _handle_connecion(), after stats_event_inc(NULL, "connections"); we make > > sock_set_blocking(con->sock, SOCK_BLOCK); and then use > > util_read_header(con->sock, header, 4096) in order to read the header of the > > request send by the client. Why putting the socket in SOCK_BLOCK mode ? Why > > receiving data from the socket byte per byte ? We know there can be >...

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