beaesguerra / agnimessenger Goto Github PK

The HeartbeatReceiver in the client needs tests written for it as well it's implementation. It's listeners should receive a proper message once the receiveMessage function is called. On hold until PR #28 is merged.

MessageSender.java in the client needs to have it's method stubs added.

The ChatReciever in the client needs tests written for it as well it's implementation. It's listeners should be receive a proper message once the receiveMessage function is called. On hold until PR #28 is merged.

Methods in the uml should be added client modules.

A JUnit test for every action handler in the client.

Setting up selectors and socket channels to receive incoming messages.

The server listener interfaces should have their methods added. Files involved are:

LoginListener.java
UserListener.java
ChatListener.java
FileListener.java
InfoListener.java
StatusListener.java

The client needs to be constructed in the main of AgniClient.java. This means writing constructors and passing in what needs to be passed in to what.

we'll be using the second one

http://stackoverflow.com/questions/2839321/connect-java-to-a-mysql-database

The Receivers in the server currently have no logic in them, they should be pretty easy to add in.

Specifically, the functions register() and their respective notifyListener() functions can be filled in pretty easily.

The files that need this are
ChatReceiver.java
notifyFileRequest.java
HeartbeatReceiver.java
InfoRequestReceiver.java
LoginReceiver.java

Message receiver needs to have it's run method implemented.

The run method is a threaded function that waits for messages from it's tcpSocket. Every message that it receives, it checks its message type, then passes the entire message onto the corresponding Receiver. This also means that the MessageReceiver needs reference to each of the receivers. It's constructor will need to be updated.

On hold until PR #28 is merged.

The StatusReceiver in the client needs tests written for it as well it's implementation. It's listeners should receive a proper message once the receiveMessage function is called. On hold until PR #28 is merged

Would have to make changes in UserManager

Once HeartbeatManager is merged in, notify StatusManager after disconnect to tell friends that the disconnected user is now offline.

(do this in StatusManager branch)

We can implement the sendMessage(byte[] message) method in MessageSender.java in the server.

This method should send the provided byte array to the server.

This class should have it's main method implemented as well so we can manually test if it works or not. It will take input for bytes we can send and then we can manually verify the client is receiving these messages through this main method.

MessageSender and MessageReceiver on both the server and client will need a connect method that gets an InetAddress for IP and an int for a port passed in.

The types for MessageParser in the server are

ip -> InetAddress
message -> byte[ ]

The DataGuards for the server are commented out becasue we don't know the types. Right now they should all be strings.

This is a mock database we can use for testing.

After PR #28 is merged we can work on register all the listeners in AgniClient.java.

Setting up selectors and socket channels to receive incoming messages.

The MessageParser in the client has it's stubs. We can implement register() and deregister(). This is waiting for PR #28

The methods for the senders right now are commented out because we didn't know the parameter types.

Since the managers are using the senders directly, these types should also be as simple as possible. I think all the parameters should be strings, if there's any question on that let me know, otherwise strings should suffice for all parameters in the senders.

The InformationReceiver in the client needs tests written for it as well it's implementation. It's listeners should receive a proper message once the receiveMessage function is called. On hold until PR #28 is merged

After PR #28 is merged, we can implement the sendMessage(byte[] message) method in MessageSender.java in the client.

This method should send the provided byte array to the server.

This class should have it's main method implemented as well so we can manually test if it works or not. The main should be passed command line arguments of the server so it can connect to the server, it'll then take input for bytes we can send and then we can manually verify the server is receiving these messages through this main method.

We can easily add the methods for client action handler. The files involved are:

ChatActionHandler.java
FileActionHandler.java
HeartbeatActionHandler.java
LoginActionHandler.java
UserActionHandler.java

We need to add stubs for all the client receiver classes. Files involved are:

ChatReceiver.java
FileReceiver.java
HeartbeatReceiver.java
InformationReceiver.java
MessageParser.java
ReceiverListener.java
StatusReceiver.java

For sending files, the protocol that we have is very weak, there is no acknowledgement whether we actually want the file or not. Any thoughts? @jeinglis @beaesguerra @mfalthaw

AgniServer.java is empty, it needs to create all the modules and them into each other as necessary.

The AgniClientView.java interface needs to have its method stub added.