> 2) The Internet is at the center, and all the end points are sitting at
> the edge, or inside of, multiple organizations implemented across
> multiple platforms. This is where SOAP and interoperability has the
> most focus. In your scenario Kevin, the fact that there is a queue at
> either end, on the other side of an intermediary proxy or protocol
> bridge is less important since the HTTP communication is the weakest
> link.
I don't think I worded this particularly well. It wasn't my intent to imply
users should set up two JMS queues and pipe messages between them using
HTTP. It was more - as you stated - that you could have a queue sitting at
the edge of the 'Intranet' before you passed the message on (or that you
could have a queue at the point you received the message). I'll have to
rethink how I worded it.
Thanks again -
Kevin
---------------------------------------------------------------------------
This e-mail message (including attachments, if any) is intended for the use
of the individual or entity to which it is addressed and may contain
information that is privileged, proprietary , confidential and exempt from
disclosure. If you are not the intended recipient, you are notified that
any dissemination, distribution or copying of this communication is
strictly prohibited. If you have received this communication in error,
please notify the sender and erase this e-mail message immediately.
---------------------------------------------------------------------------
