[Jboss-dev-forums] [Design of Messaging on JBoss (Messaging/JBoss)] - Re: Design approach for QueueBrowser

[<ovi...@jb...>]

The conclusion of this discussion thead http://www.jboss.org/index.html?module=bb&op=viewtopic&t=63511, is that all messages will be initally NACKed by the facade, and then asynchronously ACKed if the case, so all of them will be stored by the Channel. 

The difference between a message that was NACKed and a message that has never been delivered could be that the acknowledgment store remembers (M - null) for a never delivered message and (M - ReceiverID) for a NACKed message. 

I don't think there is need to change the Channel delivery strategy to distinguish between these to, but to add necessary behavior to the Channel/Acknowledgment store.





View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3876952#3876952

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3876952