levindoneto / droppedbox Goto Github PK

Needed commands:

• upload <path/filename.ext>
• download <filename.ext>
• list server
• list client
• get sync directory
• exit

ClientUser::showInterface() must return a vector<string> with the following data:

• Command
• Parameter (it is not NULL just for upload and download)

See how to use it here.

UDP by itself does not guarantee communication between client and server.

[Server] <-> [MW] <-> [Client]

It's downloading the files when they get deleted.

Break this down into pieces of development. Ping @felipetormes for doing so.

• Refactor methods for exchange of messages.
• Add utils for io in the UDP socket.

Why

The server ought to keep updated the state of each file of each user of the application.

When it has to be updated

When the following events are notified:

• IN_OPEN or IN_ACCESS (it triggers atime)
• IN_MODIFY (it triggers mtime)
• IN_CREATE (it triggers ctime)

Structure of the file

Name of the file: states.log

user1 fileName1_1 mtime1_1 atime1_1 ctime1_1
user1 fileName1_2 mtime1_2 atime1_2 ctime1_2
user1 fileName1_3 mtime1_3 atime1_3 ctime1_3
user2 fileName2_1 mtime2_1 atime2_1 ctime2_1
user3 fileName3_1 mtime3_1 atime3_1 ctime3_1
                  ...

Where it has to be placed

In the management class, and it must be used for:

• getting information: init of the droppedBox server.
• being filled with new information: every time an event which was previously discussed happens

Now it's just available to upload files from the users' sync folder.

It should throw an error, results in a segmentation fault atm

With UML diagrams and how to use the application.

It relies on the implementation of the communication using sockets UDP.

It gives a segmentation fault at the moment

connectServer -> loginServer

It relies on the implementation of notifications.

For running it: dropboxClient user IP1 PORT1 IP2 PORT2 IP PORT3