Hi!,
You are absolutely right that you can switch between ack/ackless
communication. But still to send message to another thread in a process, one
has to go out of that process, give message to JMS provider which in turn
send it to the thread in question.
As i mentioned to mark, i don't know if JMS differentiates between
inter-process and intra-process asynch communication.
If i am correct people will agree that JMS is perfect fit for inter-process,
but definiely not for intra-process.
Any thoughts/disagreement.
Punit
There is nothing in the JMS specification that says that implementations
>must use guaranteed delivery etc. As with EJB it is very possible to do
>lightweight implementations and still keep the JMS interfaces. There are
>switches in the JMS interface that lets you use different levels of
>reliability (see JSM1.0 section 4.10).
>
>/Rickard
>
>--
>Rickard �berg
>
>@home: +46 13 177937
>Email: [EMAIL PROTECTED]
>Homepage: http://www-und.ida.liu.se/~ricob684
>
>===========================================================================
>To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
>of the message "signoff EJB-INTEREST". For general help, send email to
>[EMAIL PROTECTED] and include in the body of the message "help".
>
______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
