Pavel Tcheshmedjiev

Hi Marcus,
Yes, that is exactly what you need to do.

Hi Hanna,
As far as I understand you want your clients to redirect to the new server. So if a client is not able to perform the remote call(the original remote object is no longer there, you have restarted the server), it can try to acquire a new remote object reference from the registry(in the catch section). You can also define its maximum retries.

In this case(running clients) you will have to implement a safe server stop so you can start the server again.

And finally, as Denis said, you will not gain any points of additionally complicating your tasks.

Thanks, Pafka

Your choice of RMI or serialized objects will not affect your grade, but no other approach is acceptable. In either case, the program must allow the user to specify the location of the database, and it must also accept an indication that a local database is to be used

So database location should be spesified no matter RMI or serialized objects are used. It should also be specified if the application is in standalone mode.
If in network client mode, the url must be specified - the server has already been started with the appropriate DB location.

Greetings

The maximum possible number of points is 155; the minimum to pass is 124. Section Summary Report:
General Considerations: Maximum=58 Deductions=3 Actual=55
Documentation: Maximum=20 Deductions=2 Actual=18
GUI: Maximum=24 Deductions=2 Actual=22
Server: Maximum=53 Deductions=2 Actual=51
Total: Maximum=155 Deductions=9 Certification Score=146

I joined the dark-siders with 3 tier approach and used RMI.

I want to thank you all for the wonderful forum and related books - especially Max's one and the Sun Pressed!

So THANK YOU again !!! I'll be online

Hi George,
Your arguments sound quite convincing
I'd like to ask if you documented them or it is beyond the exam's requirenments.
[ March 10, 2004: Message edited by: Pavel Tcheshmedjiev ]

Hi guys,
I guess the exception chaining is an addition to George's 1)
We catch the IOException and throw a new RNFE by using RNFE(Thowable cause) constructor, where cause is our caught IOException.
So when we catch the RNFE we can use RNFE.getCause() to identify what was the cause.
What about this approach ? I'm using it in my implementation.

Hi Satish,
There are different approaches.
What about catching the IOException and throwing a new RNFE, specifying its message or using Exception chaining.

Hi Irina,
The support will answer you in two days max.

Originally posted by George Marinkovich:
Hi Pavel,
As long as the numeric values that are stored in this field are less than (2 to the 15th power) - 1 (i.e., 32,767) then whether you use readShort() or readUnsignedShort() you would get the same answer.

Your last name is not that long. OK, you beat me by two letters, but you're 3 letters short compared to my fiancee. I don't think we'll be hyphenating our last names when we get married (28 letters if you count the hyphen).

Hi George,
Yes, 32 767 seems OK for highest value(the first bit free from duty )
About names I absolutely agree again Long names rule

The first thing you can see is that the DEBUG boolean variable is in capital letters. So this implies that it will not be changed further in the code. And the reason is that after the code is debugged, the variable is initialied to false and no debug info appears during execution. The class variable is one, and there is no need to change every if statement.

Hi Satish,
I think the main reasons for using the "this" keyword, when there is no need of it, are clarity and a good practice against argument variable/class variable conflict.

Thank you, George.
The word "numeric" at once looked like unsigned to me
I entered my full name, I thought it is a bit longer

Hello to all !
First I'd like to congretulate you for this helpful forum.
Here is my question:
1. I have in the DB file format description some lines like this:
2 byte numeric, field length in bytes
So the first approach is to interpret the 2 byte number as generic Java short. In this case if the most senior bit is 1, the short variable value will be negative.
The second approach is to interpet the 2 byte number as unsigned short.
For example if hardcoded may look like this:
int number = raf.readUnsignedShort();
In this case we double the length of the Java variable - from short to int.
So my question is does it matter which approach is used ?
If Java generic short(signed) is used, does it fail the assignment ?
Thanks, Pafka