🚀 go-pugleaf

>
Hi,
You should buffer at the receiver and send and read a lot of chars
at the same time.
Also you should do the correct error check on the read, and look for E_AGAIN.

                        bytes_read =\
                        read(sock, ucbufptr, buffer_length - bytes_received);
                        if (bytes_read < 0)
                                {
                                /* Read error. */
                                perror ("read_from_server(): read");
                                if(errno == EAGAIN) continue;
                                if(errno == EINTR) continue;
                                return 0;
                                }
                        else if (bytes_read == 0)/* EOF, connection closed by server */
                                {
                                /* we are here for example if incorrect password */
                                fprintf(stdout, "read_from_server(): EOF detected\n");

                                /* maybe close socket here */
                                return 0;
                                }
                

have a look at the internet_server.c in mcam (webcam via tcp/ip)
http://www.panteltje.demon.nl/mcam/
Not I am not using streaming, just send a frame a the time.
Still it caters for the data coming in in chunks.
(So calls to read until all data is read)
And I use select to see if data is available on the sockets.
I did try a small streaming version, but for this purpose it was not the
best solution.
Anyways, again, look at something like realplayer, it first fills a buffer,
only then it starts playing (from the buffer), while the connection keeps
the buffer filled.
The Internet cannot guarantee continuous data flow.
Please read libc.info (/usr/info/libc.info... )
it goes into much detail about all this.
Jan