This week's book giveaway is in the OCAJP 8 forum. We're giving away four copies of OCA Java SE 8 Programmer I Study Guide and have Edward Finegan & Robert Liguori on-line! See this thread for details.
As a new programmer I think I am getting confused. I have already written a Java based instant messenger for the corporate environment. however I did this when I was rather junior to java. I know see things that I could have and should have done better and would like to revisit my solution. In doing so, I see that I could make some improvement on the server side of things. How it worked before was that each person ran their own instance of the messenger, read a remote database but all messages were sent from the client machine to the others. I would like to put a server piece on the same machine as the remote database but the problem then comes when I send a message to that server piece, it has to know what to do with it depending on the type of message sent. I was thinking RMI would be the way to do this. i.e. a broadcast message would call a SendBroadcastMesg on the server, a personal message would call SendPersonal...etc... Is this a valid implementation of RMI? Then I came across a book on JMS...would this be better?? Are JMS and RMI complimentary? I don't think I've followed from what I've read very well. Any info you have would be greatly appreciated...
Ryan Headley<br /><a href="http://www.sudovi.com" target="_blank" rel="nofollow">http://www.sudovi.com</a>
Absolutely - JMS offers nice control over topics, publish/subscribe versus point to point, etc. Plus you get to learn a really significant kind of technology. Message Oriented Middleware (or MOM) is a big deal these days. I found the book Java Message Service published by O'Reilly to be very useful when I was doing SOAP messaging with JMS. Bill
Joined: Jun 28, 2000
Great! Thanx for the info. I will be returning my RMI book in favor of of the JMS one. Would like to keep both, but can't at the moment. One last question: Everyone seemed to state this as if it were a web based technology, my app is actually stand alone java. Our machines are so fast nowawadays that we don't really notice much in the way of performance. The big slow down is hitting the database. which I would prefer to let a server piece do, that my my client piece doesn't need to know any JDBC or anything.