Petinder is a social search web application that allows pet owners to like or dislike other pets, and allows pet owners to chat if both parties liked each other’s pet in the application. The app will be used as a pet's dating site.

These days, most apps are marketed as “Tinder for ____”: there is a Tinder for jobs, a Tinder for Jews, and a Tinder for people who are literally two feet away from each other. But there is no Tinder for cats and dogs in the market just yet. The current practices for finding a mate for pets are usually through asking neighbors or friends if they own, or have seen a dog of the same breed that wants to mate. There are some websites like [thedogmates.com] which claims to offer a wide choice of available mates, but they are not very popular. Finding mates for pets, especially pets that are not dogs, using the style of Tinder has not yet been developed. Our goal is to create a way for pet owners to find mates for their pets to breed with as well as also to build a legitimate social network for animals and their humans. Our small web application would be perfect for pet owners who want an easy, fun, yet serious way to find, not just a mate, but the perfect mate for their loving companion animals.

Our model is of something similar to Tinder but tailored to pets and pet owners. Users are able to profile for their pet that features photos, videos, and their pet’s “habits”. The application will then provide them with pictures of pets who are the same breed. The users can read more information about the pet, and those interested can then like it. Once a match has happened, the two pet owners can chat with each other more in depth about their pets or even set up a date.

A simple web application showing a list of pets for potential matchings and chat messages after a match has occurred.

Posts a new user using the JSON obejct in the request body. The Content-Type header must be application/json. The request body is a jsonobject with the new user's email, password, passwordConf, and displayName. To be a valid new user,password and passwordConf must match, email must not be taken by another user, and displayName must notbe empty. A copy of the created user is sent as a response.

• 415 Content-Type does not start with application/json
• 201 New user has been created
• 405 Any other HTTP Method
• 500 Internal server error

Gets a the user with the given id, or gets the currently logged in user if id is me. The user must be logged in to perform thisaction. A copy of the given user is sent as a response.

• 415 Content-Type does not start with application/json
• 200 Status OK
• 405 Any other HTTP Method
• 500 Internal server error

Updates the display name of the user with the given id, or the currently logged in user if id is me. The Content-Typeheader must be application/json. The usermust be logged in to perform this action, and can only perform it on themselves. A copy of the updated user is sent as aresponse.

• 200: Successfully edited user.
• 400: The id parameter is not a valid user ID, or the provided updates are not valid.
• 401: The user is not logged in.
• 401: The user is attempting to edit a user other than themselves.
• 415: Content-Type not application/json .
• 500: Internal server error.

Creates a new user session. Content-type must be application/json. Request body is a json obejct, that has email and password if a registered user is logged in.

• 201: New session created
• 400: The request body is not valid.
• 401: The email/password given was invalid
• 415: Content-type is not application/json
• 500: Internal server error

Ends a user sesssion. The seesion id must be "mine"

• 200: Successfully ended session.
• 403: The user is attempting to end another user's session.
• 500: Internal server error.

Responds with the list of channels that the current user is allowed to see, encoded in a JSON array.

• 200: Status OK
• 401: no X-User header in the request

Creates a new channel using the channel model JSON in the request body.

• 201: New channel created
• 401: no X-User header in the request

If this is a private channel and the current user is not a member, responds with a 403 (Forbidden) status code. Otherwise, responds with the most recent 100 messages posted to the specified channel, encoded as a JSON array of message model objects.

• 200: Status OK
• 403: The channel is private or the current user is not a member
• 401: no X-User header in the request

If this is a private channel and the current user is not a member, responds with a 403 (Forbidden) status code. Otherwise, creates a new message in this channel using the JSON in the request body.

• 201: New message created
• 401: no X-User header in the request

If the current user isn't the creator of this channel, responds with the status code 403 (Forbidden). Otherwise, updates only the name and/or description using the JSON in the request body and respond with a copy of the newly-updated channel, encoded as a JSON object.

• 403: Current user isn't the creator of the channel
• 200: Status OK
• 401: no X-User header in the request

If the current user isn't the creator of this channel, responds with the status code 403 (Forbidden). Otherwise, deletes the channel and all messages related to it.

• 403: Current user isn't the creator of the channel
• 200: Status OK
• 401: no X-User header in the request

If the current user isn't the creator of this message, responds with the status code 403 (Forbidden). Otherwise, updates the message body property using the JSON in the request body, and responds with a copy of the newly-updated message, encoded as a JSON object.

• 403: Current user isn't the creator of the message
• 200: Status OK
• 401: no X-User header in the request

If the current user isn't the creator of this message, responds with the status code 403 (Forbidden). Otherwise, deletes the message and respond with a the plain text message indicating that the delete was successful.

• 403: Current user isn't the creator of the message
• 200: Status OK
• 401: no X-User header in the request

Gets information of the pet that is owned by the current user encoded in the "X-User" header

• 500: Internal server error.
• 200: Status OK
• 401: no X-User header in the request

Creates a new pet profile for the current user using the pet information encoded as a JSON object in the request body. Responds with a copy of the newly-created pet

• 500: Internal server error.
• 201: New pet created
• 401: no X-User header in the request

Updates information of the pet owned by the current user using the pet information encoded as a JSON object in the request body. Responds with a copy of the newly-updated pet

• 500: Internal server error.
• 200: Status OK
• 401: no X-User header in the request

Deletes current user's pet profile

• 500: Internal server error.
• 200: Status OK
• 401: no X-User header in the request

Gets a list of pets for matching

• 500: Internal server error.
• 200: Status OK
• 401: no X-User header in the request

Likes a pet with the associated petID, stores the petID in the like list of the pet that owned by the current user

• 500: Internal server error.
• 200: Status OK
• 401: no X-User header in the request

Deletes the pet with the associated petID from the like list of the pet that owned by the current user

• 500: Internal server error.
• 200: Status OK
• 401: no X-User header in the request

create table if not exists users (
    id int not null auto_increment primary key,
    email varchar(128) not null unique,
    username varchar(255) not null unique,
    passhash binary(60) not null,
    firstname varchar(64) not null,
    lastname varchar(128) not null,
    photourl varchar(2083) not null 
);

Simple redis key-value store, associating session IDs with session stores, which include:

• Session start time
• User profile

MongoDB pet storage. The pet model includes:

• id (Number)
• owner (User Object)
• name (String)
• gender (String)
• age (Number)
• breed (String)
• city (String)
• intro (String)
• likeList ([Pet Object])

MongoDB message storage. The message model includes:

• id (Number)
• channelID (ObjectId)
• body (String)
• creator (User Object)
• editedAt (Date)
• createdAt (Date)

MongoDB channel storage. The channel model includes:

• id (Number)
• name (String)
• description (String)
• members ([User Object])
• editedAt (Date)
• createdAt (Date)