Work Log Begining of Time - February 9th

  Java Team - David Carothers, Kenneth Philbrick

Tasks To Complete:

David Carothers
  • Write Java Point To Point TCP File Transfer code with ui update callbacks
Kenneth Philbrick
  • Write Master Browser Index Server
  • Write Master Browser Messageing System

 

Current Status:

Date
Author
Status
Time Spent
??
Kenneth
Wrote Java AVL Tree
2 Days
??
Kenneth
Wrote Master Directory Search
6 Days
1/30/2001
Dave
Setup jdk and forte for Linux, started FTM
2.5 hours
1/31/2001
Kenneth
Writeing Cash Index Server
2 Hours
2/01/2001
Kenneth
Wrote Quero web site
3 Hours
2/01/2001
Kenneth
Working on MasterBrowser Search Cashing
5 Hours
2/02/2001
Kenneth
Debuged AVL Tree Deletion Error
3 Hours
2/02/2001
Kenneth
Working on Master Browser Messageing System
4 Hour
2/04/2001
Dave
Finished initial FileTransferManager
1.5 reading, 3 coding
2/05/2001
Dave
Learning Swing
.5 reading
2/07/2001
Kenneth
Web Crap
2 hours
2/09/2001
Kenneth
Master Browser Async Event Messageing
3 Hours
2/09/2001
Kenneth
Web Crap
4 Hours

 

Week Summary

David Carothers
  • Implementing a file transfer utility is fairly simple in Java. Opening up a few different readers and writers and run them through some sockets... I decided to make each side of the connection work on it's own thread. A good idea so that the calls to send and recieve a multi-megabyte file are non-blocking. Another design decision was to read and transmit 1400 byte chunks of files. Assuming that most hosts will run on ethernet connections with 1500 byte packet limits. This may or may not matter because of the buffered streams. I'd like to test different settings if there is some time.
  • I did give a brief moments thought to security so that people aren't just setting up reciever connections on other peoples hosts and storing files on them, etc. The hostname that connects to the ServerSocket is checked against that which the calling method passed it. So a transfer must be initiated by an agreement between hosts talking on whatever main communication link is running. Real security should be implemented there.
Kenneth Philbrick
  • So, lets see where to begin.. I will first try and write some back comments on everything.
  • The first thing I wrote was the JAVL tree.  The search of a masterbrowsers file shareing directory, is sorta our most centeral piece. So in starting the Java master browser I frist wrote a very Generic AVL tree class. A AVL tree was written becouse of its very nice self ballancing properties.  I had a little problem with my re-ballanceing code for deleteions on the AVL tree. There was one case which I origionaly wasn't checking for. To guarentee that my AVL tree's are running correctly the AVL tree right now runs in "Debug Mode", in which the AVL tree checks its self for bugs after conducting an opperation. No bugs have been seen on the AVL tree for quite some time now.
  • After writeing the JAVL tree code, I started to write the master browser directory server Java implementations. This has gone through numerous implmentations. The problem has been to design a system which easily allows both individual machines and blocks of machines to be expired, and to remove unused keys from the system.
  • Now I am working on writing the async, event system in java. I have just finished writeing a message send / reply system. The idea here is that some block of code will send a asyncronise event, then it will block for some timeout waiting for a reply, if no reply is found it will eventually wakeup. Otherwise when the message is brought back in the waiting thread will be notified.
  • So far the big thing with the Java version of one.world, is been that I have been finding that I have been re-implementing many features already found in one.world.
Back