We don't bite newbies here... much | |
PerlMonks |
Re^6: HTTPD-Password Self-Management and Recoveryby mhi (Friar) |
on Dec 04, 2011 at 19:01 UTC ( [id://941749]=note: print w/replies, xml ) | Need Help?? |
What you are describing here is the so-called lost-update problem. This can be avoided by using file-locking as you correctly pointed out. File locking does not make the server unavailable (for reading the old file) as long as you only use a write-lock and not a read-lock. A write-lock is completely sufficient in this case. Edit: The reason I don't intend to do a database-centered login is that I would actually like not to add a database and to separate the authentication from the application.
In Section
Seekers of Perl Wisdom
|
|