• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Architecture decision

 
Ranch Hand
Posts: 188
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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
reply
    Bookmark Topic Watch Topic
  • New Topic