You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by Gordon Sim <gs...@redhat.com> on 2007/09/20 14:08:42 UTC
0-10 interop & debugging
Alan Conway wrote:
> I believe C++ is encoding UUIDs correctly as 16 byte values.
I've got a fix so that the python client will as well. There are a
couple of test failures when switching over to use session_open which I
will look into then check in.
> As soon as python encoding is fixed we can do a real interop test. Does
> Java depend on this incorrect encoding? If so it also needs to be fixed
> before C++ can switch to the preview XML.
Couple of issues on java-c++ interop:
The java method types are now based on one octet each for method and
class id, though they still seem to be encoded & decoded as 32 bits
combined.
I changed the c++ to use a single byte each. This did require me to
alter the method indexes on message.empty and message.offset and the
class index on the cluster class as the original values were too large.
(I assume we will have a wholesale reallocation of ids now we have moved
to the smaller id sizes as the ids are used rather unsparingly!)
After altering the java client to encode/decode the methods encoded type
field as a short) it could correctly read in the connection.start frame
and send out a connection.start-ok.
The broker never manages to read this however. I'm still investigating
the cause, but it looks like the frame doesn't contain a value for the
response (not even an empty long string) or else is encoding field
tables and long strings with just a 16 bit size (values for both being
empty). There also doesn't appear to be an end-of-frame marker(?).
I could be wrong on all counts and will pursue this a bit further.
Consider this an invitation to share any insights you have though!
Re: 0-10 interop & debugging
Posted by Gordon Sim <gs...@redhat.com>.
Rupert Smith wrote:
> For interop on 0-10, are you going to use the same interop tests as have
> been used on the M2 branch?
Ultimately, yes. Right now I'm just trying to establish basic connectivity.
Re: 0-10 interop & debugging
Posted by Rupert Smith <ru...@googlemail.com>.
For interop on 0-10, are you going to use the same interop tests as have
been used on the M2 branch?
On 20/09/2007, Gordon Sim <gs...@redhat.com> wrote:
>
> Gordon Sim wrote:
> > The broker never manages to read this however. I'm still investigating
> > the cause, but it looks like the frame doesn't contain a value for the
> > response (not even an empty long string) or else is encoding field
> > tables and long strings with just a 16 bit size (values for both being
> > empty).
>
> Should have read some more code! The AbstractEncoder.writeTable() is
> unimplemented, so its the client-properties not the response that isn't
> in the data sent. Sending a size of zero solves that. Still no
> end-of-frame marker, which I think is what might be preventing the c++
> broker from processing the frame.
>
Re: 0-10 interop & debugging
Posted by Gordon Sim <gs...@redhat.com>.
Gordon Sim wrote:
> The broker never manages to read this however. I'm still investigating
> the cause, but it looks like the frame doesn't contain a value for the
> response (not even an empty long string) or else is encoding field
> tables and long strings with just a 16 bit size (values for both being
> empty).
Should have read some more code! The AbstractEncoder.writeTable() is
unimplemented, so its the client-properties not the response that isn't
in the data sent. Sending a size of zero solves that. Still no
end-of-frame marker, which I think is what might be preventing the c++
broker from processing the frame.
Re: 0-10 interop & debugging
Posted by Rajith Attapattu <ra...@gmail.com>.
On 9/21/07, Robert Greig <ro...@gmail.com> wrote:
>
> On 21/09/2007, Rajith Attapattu <ra...@gmail.com> wrote:
> > Try this,
> > https://svn.amqp.org/amqp/trunk/amqp_spec/amqp-spec-0-10-working.html
>
> Thanks!
>
> > This is not complete by any means, but that seems to be the best. I also
> > suggest reading the proposal attached to JIRA's that are voted.
This is for people who can't wait :)
Yes that is one approach but I was assuming that a comprehensive
> document is the key deliverable for a protocol. I am happy to wait for
> that to be produced.
Rob, I think this would take some time. Besides the doc I provided has both
correct and incorrect info in it.
It is still WIP. So the most accurate source of information is wiki
proposal + XML.
However the link I provided has good material on Execution layer, Session
stuff etc.
The following links also has good information.
New message proposal -
https://wiki.108.redhat.com/wiki/index.php/AMQP:154%2c162:Proposal
Message flow - https://wiki.108.redhat.com/wiki/index.php/AMQP:155:Proposal
--Rajith
RG
>
Re: 0-10 interop & debugging
Posted by Robert Greig <ro...@gmail.com>.
On 21/09/2007, Rajith Attapattu <ra...@gmail.com> wrote:
> Try this,
> https://svn.amqp.org/amqp/trunk/amqp_spec/amqp-spec-0-10-working.html
Thanks!
> This is not complete by any means, but that seems to be the best. I also
> suggest reading the proposal attached to JIRA's that are voted.
Yes that is one approach but I was assuming that a comprehensive
document is the key deliverable for a protocol. I am happy to wait for
that to be produced.
RG
Re: 0-10 interop & debugging
Posted by Rajith Attapattu <ra...@gmail.com>.
Try this,
https://svn.amqp.org/amqp/trunk/amqp_spec/amqp-spec-0-10-working.html
This is not complete by any means, but that seems to be the best. I also
suggest reading the proposal attached to JIRA's that are voted.
--Rajith
On 9/21/07, Robert Greig <ro...@gmail.com> wrote:
>
> On 21/09/2007, Alan Conway <ac...@redhat.com> wrote:
> > On Thu, 2007-09-20 at 13:08 +0100, Gordon Sim wrote:
> > > I changed the c++ to use a single byte each. This did require me to
> > > alter the method indexes on message.empty and message.offset and the
> > > class index on the cluster class as the original values were too
> large.
> > > (I assume we will have a wholesale reallocation of ids now we have
> moved
> > > to the smaller id sizes as the ids are used rather unsparingly!)
> >
> > This process is turning up a few spec bugs and inadequacies - are we
> > collecting them somewhere to raise with the working group?
>
> Is there an actual *document* yet that describes 0-10?
>
> (By document I don't mean an XML file).
>
> RG
>
Re: 0-10 interop & debugging
Posted by Robert Greig <ro...@gmail.com>.
On 21/09/2007, Alan Conway <ac...@redhat.com> wrote:
> On Thu, 2007-09-20 at 13:08 +0100, Gordon Sim wrote:
> > I changed the c++ to use a single byte each. This did require me to
> > alter the method indexes on message.empty and message.offset and the
> > class index on the cluster class as the original values were too large.
> > (I assume we will have a wholesale reallocation of ids now we have moved
> > to the smaller id sizes as the ids are used rather unsparingly!)
>
> This process is turning up a few spec bugs and inadequacies - are we
> collecting them somewhere to raise with the working group?
Is there an actual *document* yet that describes 0-10?
(By document I don't mean an XML file).
RG
Re: 0-10 interop & debugging
Posted by Carl Trieloff <cc...@redhat.com>.
Alan Conway wrote:
> On Thu, 2007-09-20 at 13:08 +0100, Gordon Sim wrote:
>
>> I changed the c++ to use a single byte each. This did require me to
>> alter the method indexes on message.empty and message.offset and the
>> class index on the cluster class as the original values were too large.
>> (I assume we will have a wholesale reallocation of ids now we have moved
>> to the smaller id sizes as the ids are used rather unsparingly!)
>>
>
> This process is turning up a few spec bugs and inadequacies - are we
> collecting them somewhere to raise with the working group?
>
>
>
>
I would JIRA them on jira.amqp.org and link the JIRA on this list and
copy Rafi/Rob.
Carl.
Re: 0-10 interop & debugging
Posted by Alan Conway <ac...@redhat.com>.
On Thu, 2007-09-20 at 13:08 +0100, Gordon Sim wrote:
> I changed the c++ to use a single byte each. This did require me to
> alter the method indexes on message.empty and message.offset and the
> class index on the cluster class as the original values were too large.
> (I assume we will have a wholesale reallocation of ids now we have moved
> to the smaller id sizes as the ids are used rather unsparingly!)
This process is turning up a few spec bugs and inadequacies - are we
collecting them somewhere to raise with the working group?