Hi, I have just downloaded the 1.1.3 version of the URLyBird Assignment. I have been viewing the posts here for a while and find that it can be a very helpful place to get info on the assignment. I am basically after some help on a good place to start my assigment. Im afairly new to project level development. Should I attack the RMI side of things or concentrate on the db methods. I know this is a vague post but I need some help with kicking things off. Thanks in advance. Paul
Hi Paul Welcome to JavaRanch. I would recommend you start with the db side. Once you have the database working the way you want it to, RMI will flow more easily. Trying to guess at the issues in RMI before you have worked out how to do your database could (in my opinion) be more difficult. Regards, Andrew+
Hello Paul, I also downloaded my assignment about three weeks ago. Before that, I had purchased Max's book and had gone through it once (since then, I have gone through the threading and RMI chapters twice). Like you, I was having trouble getting-off the block. I am doing more or less what Andrew is suggesting to you, i.e., work inside out. I first wrote a test program to read the datafile data correctly. You can see my threads related to it on this forum (do a search on my name "Bharat"). Once you have figured out how to read data from the datafile, you can begin to implement the data.java class with the given interface methods (I think it varies based on the versions of URLyBird. My interface is called DBMain.java while others have it as DBAccess.java. Anyway, that is the approach I am taking. I am at a point now where I am beginning to think about the RMI issues as well. Hope this helps. Regards. Bharat
Joined: Aug 11, 2003
Thanks guys, I will give it a go. I appreciate the time you have taken to help me out. See you round the Ranch.
I agree, I was taught to start with the database and work your way outward from there, with the GUI design being last. I was working with text-based testing on the database and network until pretty far into the project, which helped minimize the places bugs could surface. But that may be just my style, I know a guy who did the GUI first and saved the database locking until the end. Good luck!