rlguarino / lifeinvader Goto Github PK

http://stackoverflow.com/a/24193846

We need to call Connection.close() on all of the connection object that we create.

Don't store the password in the database, store the hash.

Add a isVisible field to the User model so when we delete a user, all we need to do is set isVisible to false, rather than true.

@zhuenink @rxl7906

Should we turn off auto-commit in jdbc and make use of savepoints and rollback to handle SQLExceptions while interacting with the database?

URL
/:user/

Display the profile page of a user.
The profile page will include the user's name and Email.

If the logged on user is a friend of the requested user, the page will display the requested users friends list, as well as the request users wall.

If the logged on user is not a friend of the requested user, then the page will display a form to request the user as a friend.

Users need to be able to request the friendship of people who are not already in their friends list.
The requested user must be notified of the pending request.
The requested user must be able to accept or reject the request.

@zhuenink @rxl7906

Should we keep this repository as a private repo? If we want to keep the repo private I would need to create a new account to host the code and migrate it there, to freee up one of my private repo slots.

If we don't keep it private, we should choose a License, I doubt anyone will look at or use the code, but just in case.

Pages like / should direct logged in users to /home when they visit them.

Pages that should do this:
/
/register
/login

"Register a new user" feature needs to be implemented.

The database creation scripts should be somewhere else other than the root of the project.

Maybe inside a /contrib directory?
Most projects have a /contrib directory that hold developer tools and scripts.
Maybe the database scripts should be in a directory /contrib/db/
For example /contrib/db/create_all.db and /contrib/db/example_insert.db

Create the design for the models.

Write the database initialization scripts.

Create the following models for Hibernate to persist to the database.

User(id, Name, DOB, Address, Email, passwdHash);
Group(id, Name, GroupSize);
Wall(Wall_ID, User_ID, Group_ID);
Post(Id, content, TimeStamp, Type, user);
Request(sender, target, isGroup);
UserRelationship(Person1_ID, Person2_ID);
Member(GroupID, PersonID);

Display user's information.

I went through and fixed some syntax and compile errors. Should be ready to merge into master. After someone looks through it.

To easier be able to search through user data, we should store the id of the user in the session variable rather than the email of the user.

Then we could use session.get("id") as the primary search key, streamlining the process of finding the currently logged in users while handling web request.

We need to insure that the Userd.email is unique in the user.email column. But It should not be the primary, in case a user would like to change their email address. Therefor we need to check every time a userd.email is inserted or updated, that no other user exists with the same email.

Display a users friends list and the friends in the list.

User Settings page where you can view and change your profile information as well as "delete" your user.

URL
/:user/friends

If the current user is a friend of the requested user, then the page will display the full friend list of the requested user.

If the current user is not a friend of the requested user, then the page will redirect to the profile page of the user. (Where the current user will be prompted to request for friendship)

Actually do it this time...

Decide how to layout the urls and what each action should do. We should have detailed designs for exactly what should be the outcome of each operation.

/:user/about

Displays user about page. Containing:
Name
DOB
Address
Email

This should check to make sure that the currently logged on user is a friend of :user

Create the db schema, and scripts for testing.

Display a wall containing all the post associated with the wall.

Remove the hibernate usage in the login implementation

If any of the jdbc operations throw an erros findByEmail will not close the connection.

URL
/:user/wall

View the users full wall.
If the current logged on user is a friend of the request user, then display the whole users wall.
If the current logged on user is not a friend then direct them to the profile page of the requested user.

There needs to be a script or a command that we can run to populate the database with test data.

Create the design for the controller interface.