Status Report: jini (20-2-2001)


Last Week

Summary:  
 

Ian

  • Finished fridge Gui (can set and view grocery list now)
  • Wrote StorageManager (used to maintain leases automatically
  • Got fridge to send email of contents and grocery list
  • Got fridge to check undelivered mail when it starts up (in case a control message was sent to the fridge when it was down)

Sherif

  • Added Remote Events, as soon as an account is added or updated
    the responsible thread is either started, or stopped SAFELY then
    restarted with the new data.
  • Added Task Manager, Service Discovery is handled by a seperate thread
    to avoid blocking of the one.box core components
  • Much more reliable system (Exception handling)

Boris

  • Router is activatable.
  • Router uses animator to contact services.
  • Router has a daemon that makes sure that undelivered mail is distributed.
  • We're starting a new level of testing.

This Week

Summary:  
 

Ian

  • Make fridge gui look a little better (maybe)
  • Test everything
  • Prepare for presentation
  • Possibly add some neat features for reliability

Sherif

  • Finalize the system, start writing the paper.
  • Take a look at Activation

 

Boris

  • TEST
  • Add activation to other services.
  • More Testing.
  • Clean up router code.
  • Write JavaDoc comments in router code.
  • Design/implement a solution to the naming/query problem.
  • Some more testing
  • Start thinking about the final paper.

Deliverables for next tuesday

Summary:  

Ian

  • Have a presentable system

Sherif

  • Work on fixing any bugs.
  • Testing the whole system
 

Boris

  • Activatable components that handle events (from lookup services.
  • Cleaned up router.

Time spent

Ian

Please go to my time tracker, click on "Universal Inbox", and log in as "guest" (no password). (I'll work put this page on this site in the future.) 

Sherif

Ian's time tracker contains my information as well.

Boris

Ian's time tracker contains my information as well.

Comments

Ian

Sherif

Boris

          Pros:

          -- It's incredibly easy to create a basic Jini service.

          -- It's easy to convert an existing service into a simple Jini service.

          -- In a lot of ways, once a Jini service wrapper is created for a class, it can then scale to enormous proportions without requiring much more jini-specific coding.

          -- Leasing provides the basis for recovery from disconnects and crashes.

          -- Multicasting lookup discovery makes it possible to locate the lookup services without prior knowledge of the network structure.

          -- Jini is built with the thought that it would have as its basis many already developed tools.

        <to be finished after I get some sleep>

 

         Cons:

         -- Though one can convert an existing service into a Jini service, more demanding requirements will force one to look for optimizations that will require additional modifications to an         existing service.

         -- Multicast lookup discovery can be a source of problems as its effectiveness is highly dependent on network topology (as was mentioned and demonstrated previously).

        <to be finished after I get some sleep>

Ian Shafer
Sherif Fanous
Boris Startsev