> There will be delays because you're limiting the browser to 1 > connection. If it tries to open more then will be rejected. It may > then wait before it tries again. If you can persuade the browser to > just use one connection and do HTTP keepalive connections to send more > than one request in that connection you'll probably get the best > performance from your configuration.
unfortunately I can't make browser not to try to make other connections. In the HTTP header I set HTTP 1.1 so a browser knows I allow a persistent connection (keepalive). I'm not a TCP/IP or HTTP expert but I think it is possible to response for SYN packet of second connection just after first one drops. Then it would work as fast as my microcontroller can. Tomasz _______________________________________________ lwip-users mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/lwip-users
