> For most browser, you don't need to save the HTTP request in RAM because most > of the time, the request will come in in one packet. I know that's not really > conforming to the standard, but it does save a lot of RAM.
> If you implement it like that, you do have to keep connection states for 2 > (or more) connections, but not the request. I just did it as you wrote. I save only pBuf pointer of second connection. > BTW, if you are that limited in RAM, you might be better off using uIP > instead of lwIP. lwIP is fine ;) > Oh, and another thought regarding speed: you might trick the browser into > using only one connection by correctly implementing HTTP/1.1 persistent > connections: the browser might think it's faster to re-use one connection if > it's a persistent one. In HTTP 1.1 browser should use persistent connection as default, but I send connection close in HTTP header of the response. I'll try to take care of this later. _______________________________________________ lwip-users mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/lwip-users
