Forums Register Login

Architecture decision: RMI or socket programming

+Pie Number of slices to send: Send
Hi,
This is probably my first post to this sub section of JavaRanch.
I just want to quickily ask about some design issues on RMI & Socket programming.
You see, my team recently developed an application which runs as an applet on the frontend. One of the fundamental duty of this applet is to do chat with the public users. You can tell that socket client/server is probably the standard approach. However, my CTO made a second approach by revamping it into running via RMI. It works! but each IE browser has to install a RMI patch.....and I'm sure browser can be a real pain unless we stick back to old fashion socket programming. Then again, socket programming needs a strong set of protocols and that itself too is a pain.
Any comments/suggestion would be welcome.

------------------
Thank you.
- Simon See
simon-ivy@usa.net
-after office hours-
necro-mani-cide
Of course, I found a very beautiful couch. Definitely. And this tiny ad:
a bit of art, as a gift, that will fit in a stocking
https://gardener-gift.com


reply
reply
This thread has been viewed 862 times.
Similar Threads
Customed JLabel and Customed JButton
writeObject to a cookie
artifacts question
Architecture decision
ejb and rational rose
More...

All times above are in ranch (not your local) time.
The current ranch time is
Mar 18, 2024 22:40:17.