Design Meeting
Discussed detail of how our project will be implemented, specifically what java classes we will need and how we will use them. We also discussed how we were going to disseminate in a reliable manner the file over the network. We did come up with one solution to basically have a take one and pass it on solution but i am in charge of seeing how this would work and also looking for alternitive solutions. Chris will be working on creating a luby code distribution testing suite. Our notes on the general overlay of our java classes are as follows.
- Java Classpaths
- lerao.mimir
- client — In charge of interacting with user and initiating file transfers
- ui — In charge of how users interact with the system
- file — In charge of manipulating the file including encoding and decoding
- header — holds the encoding header
- data — holds encoded and decoded data
- block — Contains file header,data and id
- metadata — In charge of controlling all the data
- ui — ability to configure and view the status of the network
- crypto — handles all cryptographic functions
- network — handles all shared network functions
- storage — handles saving data from the network to disk and vice-versa
- client — In charge of interacting with user and initiating file transfers
- lerao.mimir
No comments yet. Be the first.
Leave a reply

