YouAreEll

Under-A-Rock

Client HTTP/REST API for UnderARock

The Point

• You are to write a command interpreter using the provided SimpleShell class.

• You're going to create a way

  • for commands to be typed into your shell,
  • to read the typed commands and arguments,
  • to send them off to the Under-A-Rock server using a REST API over the HTTP protocol,
  • to read the JSON data returned from the URL call,
  • to print it out nicely formatted for your user.

• Under-A-Rock acts a little (very little) like a twitter server or chat server.

  • You register your name and github id by creating an ID JSON payload (see below) and POSTing it to the server.
  • You can GET all the ids registered by sending a GET request to the same URL.
  • Once you've received all the ids, you can send messages to the world or to a specific Github_id.

• You can send a message to the global timeline by POSTing a Message JSON object to the URL below.

  • If you leave the to id field empty, the message is to the world.
  • If you fill out the the JSON template with a valid github_id in the to id field of the JSON payload, then that message is addressed to that friend.
  • Yes, all messages can be seen by users of the system.
  • There are JSON templates below for both Ids and Messages.

• When you send a new Message or Id JSON object to the server, it records it, and fills in one or two fields.

  • A Message gets an assigned sequence number and a timestamp of when it was received by the server.
  • An ID object gets a "user id" field assigned to it.
  • Any sequence number, timestamp or userid you put into a JSON template gets overwritten by the server when you POST it.

• You're going to create a series of REST API handlers that will each perform a specific command.

  • Each one of the command methods will then call a even lower-level method that makes a certain kind of HTTP request (GET, POST, PUT) to specific filled-in URL.

• The Under-A-Rock Server can be reached at http://zipcode.rocks:8085 Everyone uses the same server.

  • There are two segments to the API and two kinds of commands in the shell, the ID segment and the Messages segment.

• You can explore several ways of doing the HTTP URL calls to the server, using the one of these:

  • Apache HTTP Client Library
  • Unirest for Java
  • Square's OKHttp
  • Core Java:
    • URL
    • HttpURLConnection

• Be prepared to defend your choice if which HTTP client library you chose, with reasons why you chose it.

  • You should also create some unit tests for your REST API handlers.

• It's possible you may also need to understand some of what the Jackson package does.

IDs

ID commands in shell

• In the shell, ids should return a formatted list of the IDs available to you.
• ids your_name your_github_id command should post your Name and your GithubId to the server.
• If you do this twice with two different Names, but the name GithubId, the name on the server gets changed.

-

The IDs API is:

URL: /ids/

• GET : Get all github ids registered
• POST : add your github id / name to be registered
• PUT : change the name linked to your github id

json payload for /ids/ - this is a sample

{
    "userid": "-", // gets filled w id
    "name": "Kris",
    "githubid": "xt0fer"
}

Example:

If I type cmd? ids Kris xt0fer into the shell, your command processor creates a JSON object which looks like:

 {
     "userid": "-", // gets filled w id
     "name": "Kris",
     "githubid": "xt0fer"
 }

and send it as the body of a POST request to http://zipcode.rocks:8085/ids/

Messages

Message comands in shell

in the shell

• messages should return the last 20 messages, nicely formatted.
• messages your_github_id should return the last 20 messages sent to you.
• send your_github_id 'Hello World' should post a new message in the timeline
• send your_github_id 'my string message' to some_friend_githubid should post a message to your friend from you on the timeline.

the Messages API is:

URL: /messages/

• GET : Get last 20 msgs - returns an JSON array of message objects

URL: /ids/:mygithubid/messages/

• GET : Get last 20 msgs for myid - returns an JSON array of message objects
• POST : Create a new message in timeline - need to POST a new message object, and will get back one with a message sequence number and timestamp of the server inserted.

URL: /ids/:mygithubid/messages/:sequence

• GET : Get msg with a sequence - returns a JSON message object for a sequence number

URL: /ids/:mygithubid/from/:friendgithubid

• GET : Get last 20 msgs for myid from friendid

json payload for /messages/ these are samples, one to a specific friend, one to the timeline.

[
  {
    "sequence": "-",
    "timestamp": "_",
    "fromid": "xt0fer",
    "toid": "kristofer",
    "message": "Hello, Kristofer!"
  },

  {
    "sequence": "-",
    "timestamp": "_",
    "fromid": "xt0fer",
    "toid": "",
    "message": "Hello, World!"
  }
]

Example:

if I type

send xt0fer 'Hello old buddy!' to torvalds

into the shell, your command processor creates a JSON object which looks like:

{
	"sequence": "-",
	"timestamp": "_",
	"fromid": "xt0fer",
	"toid": "torvalds",
	"message": "Hello old buddy!"
}

and send it as the body of a POST request to http://zipcode.rocks:8085/ids/xt0fer/messages/

Part Two

What's that ProcessBuilder stuff about? In the SimpleShell class, take a look. How can that be used as a pattern to use threads to make the API calls and wait for the response? Maybe launch a new thread on every request?

Part Three

Build a better set of commands. Make the "fromid" intrinsic, so it isn't needed on the various shell commands. Add a feature where you can send messages by someone's name. Create a means where the client watches the server for any private messages to you and only prints them once. Add another command that watches the global stream and only prints messages once.