• 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

Chat Application Architecture?

 
Ranch Hand
Posts: 42
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Can anybody help me out about what could be the best architecture for developing a chat application like MSN Messenger (for intranet as well as if possible for the internet as well).
I know RMI or .net can be very useful but can anybody tell me more clearly that what threading issues and client-to-server or server-to-server communication should be taken into consideration ??
Please help me in detail.
Thx in advance
bye
Badal
 
Ranch Hand
Posts: 42
Hibernate Oracle Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi Badal,
According to my study
There are two ways to develop Chat Application.
1.Using Sockets and Streams
2.Using JMS

Using Sockets guarantees the delivery of the message but this is often used because most of the firewalls block socket connections.
Using JMS for a chat application is an overkill because a simple chat application doesnt need J2EE architecture and on top of that it effects the application performance

 
Oh. Hi guys! Look at this tiny ad:
a bit of art, as a gift, that will fit in a stocking
https://gardener-gift.com
reply
    Bookmark Topic Watch Topic
  • New Topic