Originally posted by Roberto Perillo:
URLyBird 1.4.0?! Had never heard of it!!!
[ December 19, 2008: Message edited by: Roberto Perillo ]
Originally posted by Jeffry Kristianto Yanuar:
RMI is better and simpler unless you're the one who likes to make your life harder just like me.
If you want to use RMI, don't use the server thread object that handles the client as the owner of the locked record because it is not guaranteed that the same server thread object will serve the same client.
Anyway, I never heard that version of URLyBird, maybe it is the new version of URLyBird.
Good Luck !!!
Jeffry Kristianto Yanuar (Java Instructor)
SCJP 5.0, SCJA, SCJD (UrlyBird 1.3.2)
[ December 20, 2008: Message edited by: Jeffry Kristianto Yanuar ]
I still took Sockets(besides my personal preference ) because of this phrase from my assignement "In the future, URLyBird wants to move into Internet-based marketing, and hopes to be able to accept bookings direct from customers over the web. " and, what Sockets can offer over RMI, is performance, better control of the protocol, and because I did't have to concern about client disconnection as the server would receive an exception by default in such case and last but not least, offers more flexibility for client's platform(which of course, stands up for the future plans of URLyBird, not for the present).
Now my question is, are all my arguments even valid, or are they week since RMI is more recommended, and i should after all redesign to RMI.
The next question would be, as I only red the RMI solution described in "SCJD Exam with J2SE5", but didn't try to figure out a RMI solution for my assignment, what special things are to be concerned about in case of Sockets or in case of RMI, for my business layer, since i have seen posts that mention the fact that designing the business layer depends on it?