[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [lwip-users] webserver withmethod=POST
From: |
Goldschmidt Simon |
Subject: |
RE: [lwip-users] webserver withmethod=POST |
Date: |
Wed, 25 Jul 2007 13:14:41 +0200 |
> Ok, it's confirm what I thought. With the default
> MEMP_NUM_NETCONN(4), when you're browser read the main doc,
> it see(parse) there is several "sub docs" to read. Most of
> modern browsers try to accelerate the response time by
> sending multiples "GET" in parallel (in the same time). Your
> target receive all, but since you process each request in a
> sequential order (you don't launch a thread for each one,
> which is usual in embedded targets), if your target if too
> "slow", you don't call netconn_delete fast enought, and the
> one or several request will failed since there is not enought
> netconn in the memp pool. MEMP_NUM_NETCONN=10 is a good value
> since most of browsers can send max. 8 requests in the same
> time (and you use one for listen).
Could this also a limitation that our httpd closes the TCP connection
after sending one file whereas most 'modern' webservers re-use a TCP
connection for multiple requests?
This can be achieved with our httpd by not actively closing the pcb
after sending but only closing after a timeout or as a response to
a client closing its side of the connection (i.e. http_recv() being
called with a pbuf of NULL).
Simon