The interop case that I was thinking about was the replyto field currently
in the basic content class.
If clients don't have a common understand of how that field is encoded then
I don't think that field is very useful?
RG
|---------+---------------------------->
| | Gordon Sim |
| | <[EMAIL PROTECTED]>|
| | |
| | 25/09/2006 11:38 |
| | Please respond to|
| | qpid-dev |
|---------+---------------------------->
>--------------------------------------------------------------------------------------------------------------------------------|
|
|
| To: [email protected]
|
| cc:
|
| Subject: Re: Qpid URL Formats [ was Re: A question for the ActiveMQ
chaps on the list...] |
>--------------------------------------------------------------------------------------------------------------------------------|
Martin Ritchie wrote:
> We currently have a URI format that is in use in the Java implementation.
>
> I have created a wiki page that describes this format.
>
> http://wiki.apache.org/qpid/URLFormats
>
> Comments and feedback would be great. If we can come to an agreement on
the
> format then we can suggest it to the AMQP WG as they do not currently
have
> a defined format. Such a format will be required for interoperability.
I disagree. Such a URL format seems relevant only to the API in use. It
is only required for interoperability between different
implementations of that same API and even then merely allows you to
leave your configuration unchanged between implementations.
It is currently only used in the JMS adaptors API. As the format is not
standard across JMS implementations, an application using the JMS APIs
in conjunction with qpid would still need to revise their configuration
if they move to (or from) an alternative JMS implementation.
This communication is for informational purposes only. It is not intended as an
offer or solicitation for the purchase or sale of any financial instrument or
as an official confirmation of any transaction. All market prices, data and
other information are not warranted as to completeness or accuracy and are
subject to change without notice. Any comments or statements made herein do not
necessarily reflect those of JPMorgan Chase & Co., its subsidiaries and
affiliates.
This transmission may contain information that is privileged, confidential,
legally privileged, and/or exempt from disclosure under applicable law. If you
are not the intended recipient, you are hereby notified that any disclosure,
copying, distribution, or use of the information contained herein (including
any reliance thereon) is STRICTLY PROHIBITED. Although this transmission and
any attachments are believed to be free of any virus or other defect that might
affect any computer system into which it is received and opened, it is the
responsibility of the recipient to ensure that it is virus free and no
responsibility is accepted by JPMorgan Chase & Co., its subsidiaries and
affiliates, as applicable, for any loss or damage arising in any way from its
use. If you received this transmission in error, please immediately contact the
sender and destroy the material in its entirety, whether in electronic or hard
copy format. Thank you.
