[Jboss-dev-forums] [Design of Messaging on JBoss (Messaging/JBoss)] - Synchronous vs. asynchronous NACK when client refuses delive

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

I am starting a new design thread here, to separate it from the Remoting issue that sparkled it (http://jira.jboss.com/jira/browse/JBREM-93): 

anonymous wrote : 
  | Use case:
  | 
  | I am using a push callback to synchronously deliver a message to a JMS Client (MessageConsumer). My server-side consumer endpoint receives the message from the messaging core and synchronously invokes callbackHandler.handleCallback(...). The server-side thread is blocked until the push either succeeds or fails.
  | 
  | This invocation eventually reaches my callback handler on the client-side. However, the callback handler should be able to refuse the message: for example, nobody is blocked in a receive() and there is no message listener. There should be a way to politely say: yes, I have seen your message, but I don't need it and I don't want it, and here's my NACK.
  | 
  | With the current InvokerCallbackHandler.handleCallback() signature (public void handleCallback(InvocationRequest invocation) throws HandleCallbackException), the only way for the callback handler to send a NACK is to throw a HandleCallbackException
  | 
  | 

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

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