In this project, we venture into cookies and application servers. You will create a database of users that allows the users to be recognized after providing a password only once. The passwords are maintained by a database manager (or an application server in other words). You can just use a flat file for the database of users; however, you may want to explore MySQL with JDBC if you know what they are. If not, then forget it, and just use a file. Here is a scenario: Bob accesses our Web server using his Web browser. The Web server sends a response message with a cookie and a form asking Bob to log on. Bob enters a name and password using the HTML form (from the browser of course) and clicks on the Submit button. The Web server connects to the application server and asks it to store the password along the user name in the database. Next time Bob accesses the Web server, the server obtains the cookie and asks the application server to verify Bob's authenticity. If Bob does not have to log on; the server should display a message: "YOU ARE IN!". The password should expire with certain frequency. If the date associated with the password's storage expires (that is, the user did not log on for some time), force the user to log on again. In this exercise, we will not worry about security. The password can be saved and transmitted in a clear - textual - form. Use UDP between the Web server and the application server.
Rent A Coder requirements notice: As originally posted, this bid request does not have complete details. Should a dispute arise and this project go into arbitration "as is", the contract's vagueness might cause it to be interpreted against you, even though you were acting in good-faith. So for your protection, if you are interested in this project, please work-out and document the requirements onsite.
1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done.
2) Deliverables must be in ready-to-run condition, as follows (depending on the nature of the deliverables):
a) For web sites or other server-side deliverables intended to only ever exist in one place in the Buyer's environment--Deliverables must be installed by the Seller in ready-to-run condition in the Buyer's environment.
b) For all others including desktop software or software the buyer intends to distribute: A software installation package that will install the software in ready-to-run condition on the platform(s) specified in this bid request.
3) All deliverables will be considered "work made for hire" under U.S. Copyright law. Buyer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site per the coder's Seller Legal Agreement).