Re: don't completely get it with JMS ...

The deal with JMS is that there are at two different, popular methods
used in Messaging, and JMS supports both of them. So in MQ you have
Queues accessed typically via RMI.

Other vendors support Topic style Messaging.

So the one that sends the message is called a publisher when sending
one-to-many, recieved by a Topic.

A one-to-one relationship is supported by a Sender placing a message
for a Queue.

Session is used by both the Queue and Topic receivers, and by the
Publisher and Sender. The Connection is just typically the JNDI
supplied access to the Messaging server.

HTH,
iksrazal
http://www.braziloutsource.com/

.

Relevant Pages

  • Re: JMS: the confusion BEFORE writing my first Application.
    ... queuing services buit in? ... >> I read in the sun jms doc that jms is the java interface to ... you need a messaging service that has a JMS-conforming interface. ... even if i didnt have to ...
    (comp.lang.java.programmer)
  • Re: OpenJMS and communication to non-JMS
    ... but I probably don't want to run tomcat either. ... JMS, but is not primarily a JMS service, if you get my meaning. ... I'm sure there are messaging servers that support JMS as well as have C/C++ libraries. ...
    (comp.lang.java.programmer)
  • Re: Thread Checking the Queue data in an infinite loop
    ... Note that IOCPs don't have "spurious wakeups". ... I've done some fairly intense high-performance interthread messaging using IOCPs, ... access to the Queue. ...
    (microsoft.public.vc.mfc)
  • Re: PeekMessage, DispatchMessage in C# ??
    ... I have a queue q. ... is a simple callback mechanism that is described as messaging. ... > time (thread concurrency control) you should be ok. ... >> Hi Alex, ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: Threading in .Net...
    ... the way it provides messaging between threads is a little ... monitor like the critical section variables to protect the global ... item is placed on the queue, ... When it's done it can reset the ManualResetEvent and wait until ...
    (microsoft.public.dotnet.languages.vb)