> Typically, a browser will send multiple overlapped GET requests for
> resources (pictures) on the same page.
>

Good point! I guess the browser sends each request out a different port
and the server responds back to that port, allowing the browser to sort
stuff out. I'm just sending a single html page in response to a GET
request. I pass the HTML as a string into this:

void SendWebPage(char *string){
// Send HTTP headers, then send string.
 fprintf(pradio,"HTTP/1.0 200 OK\r\nContent-type:
text/html\r\nContent-Length: %d\r\n\r\n",strlen(string)); // send header
 fprintf(pradio,"%s",string);   // send page
 fflush(pradio);    // flush the buffer
}


If the browser keeps the connection alive, does it just keep several
alive, then reuse them after the server responds?

It LOOKS like my approach will work as long as an HTML page does not
"call" another as it is rendered.

THANKS for the ideas!

Harold


-- 
FCC Rules Updated Daily at http://www.hallikainen.com - Advertising
opportunities available!
-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist