Hi, a system I used to work with, happened to solve this issue in a very elegant way. You need a tag, a hidden variable in your form, whose value will be received by the browser when loading the form (SSI) and will be incremented by the system at every form submission (CGI). If the received tag does not match the one in the system, then there's been a collision where one configurating user is trying to submit changes based on old data, and another configurating user has already submitted changes in between. The login/logout suggested by Simon can be easily done with a couple CGIs and a timer, and you can also use user authentication. My fork of this web server supports all this (raw API only). http://scaprile.ldir.com.ar/cms/el-ingeniero/open-source-projects-im-working-on/lwhttpd/ Regards --
_______________________________________________ lwip-users mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/lwip-users
