Noam Weissman wrote: > Is there a way to limit the number of concurrent HTTP connection, say to one ?
Listen backlog does not help much here. You'd have to close the listener after accepting the first connection. Reopening it later might require SO_REUSE though. Alternatively, you could set MEMP_NUM_TCP_PCB to 1 to allow only one TCP connection at all. I guess you'd additionally have to increase the prio of the connection pcb to prevent a new connection from closing the existing one (see tcp_alloc/tcp_kill_prio). However, in both cases, the browser will still try to open more than one connection and get back a RST. I don't know if resources scheduled over such an attempted connection are retried on a different connection later? Last time I tried with Chrome, they were just missing when the page was rendered :-( Simon _______________________________________________ lwip-users mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/lwip-users
