Hi,
Sure I am keen to help out where I can.
I am fortunately able to focus on Qpid quite a bit at the moment.
RG
|---------+---------------------------->
| | "Rajith |
| | Attapattu" |
| | <[EMAIL PROTECTED]|
| | om> |
| | |
| | 20/09/2006 16:30 |
| | Please respond to|
| | qpid-dev |
|---------+---------------------------->
>------------------------------------------------------------------------------------------------------------------------------|
|
|
| To: [email protected]
|
| cc:
|
| Subject: Re: To extend or not (was RE: QPID/HermesJMS)
|
>------------------------------------------------------------------------------------------------------------------------------|
Robert,
I guess thats where the misunderstanding started. I used the wrong choice
of
words.
Instead of saying AMQP client API, I should have used AMQP protocol level
API :)
>Are you planning on fleshing it out on a branch?
Yes that would be a better approach so I want disrupt the trunk in anyway.
However I am tied up this week and can only start looking at it next week.
I will also start a thread on this topic and I am counting on you for
support and comments/ideas/suggestions
Regards,
Rajith
On 9/20/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]>
wrote:
>
> Yes, I think that a protocol-level API is fine. I had thought you were
> proposing something at a higher level.
>
> Are you planning on fleshing it out on a branch?
>
> RG
>
>
> |---------+---------------------------->
> | | "Rajith |
> | | Attapattu" |
> | | <[EMAIL PROTECTED]|
> | | om> |
> | | |
> | | 20/09/2006 15:49 |
> | | Please respond to|
> | | qpid-dev |
> |---------+---------------------------->
>
>
>------------------------------------------------------------------------------------------------------------------------------|
>
> |
|
> | To: [email protected]
>
|
> |
> cc:
|
> | Subject: Re: To extend or not (was RE:
> QPID/HermesJMS)
|
>
>
>------------------------------------------------------------------------------------------------------------------------------|
>
>
>
>
> Greg,
>
> What I am also pushing is for a protocol level API.
> Even if we don't document this or promote this API, I still think from a
> design POV we need to have a cleaner seperation.
> So why not have protocol API and then have that 'extended JMS API' if you
> will.
>
> But lets not kill the idea of a protocol level API.
>
> Does this sound like a reasonable compromise???
>
> Regards,
>
> Rajith
>
> On 9/19/06, Gordon Sim <[EMAIL PROTECTED]> wrote:
> >
> > Robert Greig wrote:
> > > Unless what is being proposed is
> > > what I read into Gordon's comments (I don't want to put words in your
> > > mouth so let me know if I'm misrerepresenting you Gordon) which is a
> > > strictly protocol-level API.
> >
> > Yes, I was talking about a protocol-level API.
> >
>
>
>
>
> 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.
>
>
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.
