aspose file tools*
The moose likes EJB and other Java EE Technologies and the fly likes Reliable Messaging in Java 5 Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Java » EJB and other Java EE Technologies
Bookmark "Reliable Messaging in Java 5" Watch "Reliable Messaging in Java 5" New topic
Author

Reliable Messaging in Java 5

jyoti misra
Greenhorn

Joined: Apr 09, 2012
Posts: 6
Hi,

How can we achieve relaible messaging between server and client. Say, that the client is connected through a 3g session and there is intermittent network drops. In such a case ajax control on the client always show progress bar because they dont get all the packets in one go as the session keeps dropping.

Appreciate a quick response.
TIA !
Henry Wong
author
Sheriff

Joined: Sep 28, 2004
Posts: 18717
    
  40

jyoti misra wrote:
How can we achieve relaible messaging between server and client. Say, that the client is connected through a 3g session and there is intermittent network drops. In such a case ajax control on the client always show progress bar because they dont get all the packets in one go as the session keeps dropping.



This is a pretty open ended question -- as it will depend on what you mean by "reliable messaging". In general, I am assuming you mean the quality of service ("reliable messaging" is gap detection and gap fill of message streams provided by messaging APIs), so, I would say, in Java, you should use JMS, and uses a messaging provider that suite your needs.

However, you also mentioned AJAX, which implies javascript, implies a web connection (http(s) over TCP), etc., which is a different question entirely.

Henry


Books: Java Threads, 3rd Edition, Jini in a Nutshell, and Java Gems (contributor)
jyoti misra
Greenhorn

Joined: Apr 09, 2012
Posts: 6
Henry,

Thanks for the response.
Let me clarify -
Reliable messaging implies that when the producer sends out a message (broken into packets) for the consumer to consume, they should all be delivered to the consumer. In realistic scenario if there are packet drops then those packets should be resent to ensure that the whole message got delivered.
And the framework is that on UI we have extjs/html5 and at backend we have soring/hibernate.

As per your response JMS can help us in getting this reliable messaging. Please also clarify what messaging providers can be used for using JMS.

Please also let me know if there any other solutions in the market to achieve this kind of reliable messaging.

Appreciate your help.

TIA!
E Armitage
Rancher

Joined: Mar 17, 2012
Posts: 892
    
    9
jyoti misra wrote:Henry,

Thanks for the response.
Let me clarify -
Reliable messaging implies that when the producer sends out a message (broken into packets) for the consumer to consume, they should all be delivered to the consumer. In realistic scenario if there are packet drops then those packets should be resent to ensure that the whole message got delivered.
And the framework is that on UI we have extjs/html5 and at backend we have soring/hibernate.

As per your response JMS can help us in getting this reliable messaging. Please also clarify what messaging providers can be used for using JMS.

Please also let me know if there any other solutions in the market to achieve this kind of reliable messaging.

Appreciate your help.

TIA!

One approach to reliable messaging over an unreliable infrastructure is WSRM

http://en.wikipedia.org/wiki/WS-ReliableMessaging
http://docs.oasis-open.org/ws-rx/wsrm/200608/wsrm-1.1-spec-cd-04.html
jyoti misra
Greenhorn

Joined: Apr 09, 2012
Posts: 6
Hi E Armitage,
Thanks for the response. WSRM is indeed the solution I was looking for.
Can you also please let me know which are the good implementations of WSRM?
One is Apache Sandesha2. Please highlight if there any other better solutions available in the market.

TIA!
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Reliable Messaging in Java 5