State management, configuration and installation of web application

Version C

A web log (blog) with flooding prevention

• Investor requirements:
• "There are two kinds of users who can take part in the blog: authorised and anonymous"
• "Authorised users can access the blog with login and password, which can be obtained during registration. There has to be some way of dealing with forgotten passwords."
• "Each of the authorised users has his own thread, which he can manage, i.e. remove the unwanted posts and edit his own posts"
• "Each of the posts is signed by its author, for the authorised user automatically with his login; the anonymous user has to put the nickname in the textbox."
• "The posts in each thread are reverse chronologically ordered. There is a posting date and time by each post."
• "Adding posts can be performed by anyone in the Internet"
• "Flooding prevention: The anonymous users cannot add posts more often than each five minutes. - this does not need to be a unbreakable restriction, but such a evil user should find the prevention a serious obstacle."
• "Administrator access: the administrator has the right to remove each post and each thread from the blog"
• "The registered user can log in from each page in the service. After logging in the displayed page should be the same as before."
• "In case the session expires during post writing, such a situation, that the registered user mistakenly posts a anonymous message, should be prevented. In other case than writing a message, the user should be informed, that the session had expired, but the appearing page should be the same he had expected."
• System administrator remarks:
• "User data should be stored in the data and the posts in the posts subdirectories."
• "Administrator login and password should be stored in Web.config, all other users cannot access the administrator pages."
• Marking remarks:
• The entire project should be published over the Internet - provide the URL with the solution.
• The project should be user-friendly - avoid situations in which the user finds himself lost.
• Writing code, which is already implemented in .NET can result in lower marks.
• The investor is always right, independently on how precisely does he utter his ideas.