|
From: | brak brak2 |
Subject: | Re: [lwip-users] disconnect - connect delay |
Date: | Fri, 1 Apr 2011 17:56:44 +0200 |
>>I think you'd be better limiting the number of connections by modifying >>the webserver to only accept one at a time rather than trying to enforce >>this at the TCP level. > > I agree and have done so successfully by simply closing the multiple > connection in the accept callback. I even use the connection to post send > back a 'Multiple Connections Refused' error response that the PC programming > picks up and can notify the user why the connection is closed. Did you use it in HTTP server code? When I abort the multiple connection in the accept callback the web browser don't load all the webside elements. If browser get RST flag in TCP packet it doesn't try to download the element again. In firebug it is shown as Abort state instead of "200 OK". As you can see aborting connection can't be use in HTTP protocol. Or maybe I'm doing something wrong. Tomasz
[Prev in Thread] | Current Thread | [Next in Thread] |