[ Index ]
[ Individual Project ]
[ Placement Presentation ]
[ Timetable ]
[ Index ]
[ Research ]
[ Schedule ]
Week 17 - Status Report
25/02/2002 - 03/03/2002
Last Updated: 26th February 2002
Log
Group Meeting Notes - 25/02/2002
Discussion of Vlad's project (similar to mine but on C#) got me thinking on how to handle binary compatibility checking when a library depends on other libraries on the server.
- Approach 1 - If the classloader detects a class that is not in the
Jar file for that library it ignores it. This would make the binary compatibility checking for the dependent libraries a separate process simplifying the checking process. It does mean that the Jar classloader has to be extended to ignore requests for classes not contained in its JAR and handle
ClassNotFoundExceptions gracefully. It also means after checking a library needs to update information for its dependents as well.
- Approach 2 - When the classloader encounters classes in dependent libraries it loads them. This approach is more 'elegant' since it allows the operation to be just one step, it does create the possibility for circular errors arising if two classes depend on each other.
Second Marker Meeting Notes - 26/02/2002
Met with Jeff Magee to discuss the current state of my project. He had some concerns that I was leaving the client side work until after the exams and suggest I create a fully working demo by the end of the term.
Suggestions
- Focus on creating client side code and produce a rough demo that demonstrates all functionality by the end of the term.
- Work on report in parallel to coding.
- Make sure the final demo is visual.
- Make sure the final demo is scripted so it is similar to a presentation.
After receiving this feedback I will alter my schedule. Since getting a working demo is key I will set aside inter-library dependencies until after the break. Key tasks now include getting ta basic client up and running, writing the protocol adapter for the server and catching up on my report.
This should leave me in a state will a rough version of everything by the end of the term. This means the time spend after the exams would be cleaning up the code and report and adding the advanced features.
First Client Design
Documentation Snapshot
Code Snapshot
Miles Barr <miles@milesbarr.com>
