> -----Original Message----- > From: [email protected] [mailto:lwip- > [email protected]] On Behalf Of > [email protected] > Sent: Tuesday, May 12, 2015 3:19 PM > To: Mailing list for lwIP users > Subject: Re: [lwip-users] Single connection with "httpd" web server > > Info wrote: > > Now I would like to limit the number of connections to one, that > means > > only one user can connect to the web server (and can make changes on > > the configuration of the embedded system). > > That's not a good idea. It's just not the way HTTP and browsers work.
1. HTTP is just a protocol, nothing to do with the number of concurrent connections; it will work perfectly fine if you limit the connections to one at a time. 2. Whether or not a browser will create multiple connections depends on your HTML which you can fully control, so I don't think this is such a bad idea at all. BTW, once you try running a secure web server on an embedded target, the 16-32kB per TLS connection (WolfSSL) will make you very quickly appreciate the benefit of limiting the number of concurrent connections. -Z > Every browser will open multiple connections and expect them to > succeed. > It won't use the first (successful) connection to load files that fail > to download on a 2nd connection. > > You should instead implement a login/logout/timeout procedure to limit > configuration changes. However, that's not provided as a service by our > webserver (yet?). > > Simon > > _______________________________________________ > lwip-users mailing list > [email protected] > https://lists.nongnu.org/mailman/listinfo/lwip-users _______________________________________________ lwip-users mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/lwip-users
