Passed ... :-) ....

I would like to thank everybody that make this

group so rich with a lot of steps and tips to

make the right decision in the project.

Yesterday I received my results and I have to thank the

group,

good luck for every body.

My result was:
The maximum number of points is 400, to pass you need a score of 320. Section Summary:
Section Max Actual Points Points
General Con: 100 100
Documentation: 70 70
OOD: 30 30
GUI: 40 40
Locking: 80 65
Data Store: 40 40
Network Server: 40 20
Total: 400 365

Gustavo Dutra Martins

Congratulations, Gustavo !

Originally posted by Gustavo Dutra:

Locking: 80 65

Congratulations! What an odd score for locking. Could you describe your implementation of it?
[ May 18, 2005: Message edited by: Titus Barik ]

365/400 Congratz !!!

Congrats~

Congratulations Gustavo

Congratulations

Hi Titus,

The lock is the real problem of the application,

I implemented the lock in two phases,

this happens because of the lock method, this

EVIL method only receive two arguments, the identification

of the client was not informed.... SO...... the only form

to make this work is to set an attribute value, but the attribute

is not thread safe, so you have to synchronize the first part

(the lock set) and then lock again (the lock object) to implement the

wait/notify protocol.... with this implementation you make the acquire lock

thread safe....

I did not receive 100% in the lock problem....

I think they want a lock manager or I made a mistache.... I don�t know...

well....

It doesn�t matter...

now is only celebration

I hope it helps you,

Gook luck

Gustavo

Originally posted by Gustavo Dutra:
The lock is the real problem of the application,
...
I did not receive 100% in the lock problem....

I think they want a lock manager or I made a mistache.... I don�t know...

well....

It doesn�t matter...

now is only celebration

I hope it helps you,

Gook luck

Gustavo

Congratulations on a great score, especially the locking. I have come to think that the marking shares a lot in common with figure skating, its subjective and totally up to the judges.

Again congratulations

so you have to synchronize the first part

(the lock set) and then lock again (the lock object) to implement the

wait/notify protocol.... with this implementation you make the acquire lock

thread safe....

I came across an example by Alain Troitter and in his locking example - there is a synchronized lock method. In the synchronized method he doesn't acquire the lock for the hashmap (the locked records) before adding elements in to that table or deleting it from the table. Is this the right way to do it?

Hi Muthaiah,

If the method itself is synchronized, and there is only one instance of the class, then only one thread can ever be adding lock details to the collection. So this will work.

I don't believe it is the best way of handling this though - I believe you should be limiting your synchronized code to the smallest possible block, and synchronizing on an object that makes sense for the synchronization (so the Collection for locking and the RandomAccessFile for file I/O (or similar)).

Regards, Andrew

I have moved this post to the Sun Certification Results forum. You can now find it here.

Regards, Andrew

Congratulations!!!

Well Done!!!

congratulations and enjoy!