I've been trying to get the .Net and Java clients passing field tables to each other and ran into a NotImplementedException in the Qpid.Buffer.FixedByteBuffer class in the slice method. This has lead me to start taking a more in depth look at some of this buffer stuff, which as you rightly point out Tomas is a bit of a mess. I'm wondering why a FixedByteBuffer wraps a HeapByteBuffer and why we have all these different buffer implementations. It looks to me like this stuff has been ported over as a quick and dirty hack from Mina code.
Tomas, I'm just wondering if you've done anything with any of this yet or just left it well alone (I certianly don't blame you)? I'm planning to go through it all , document it so that I can comprehend it, hopefully just make a few small changes to the field table stuff working asap and then we can decide how to refactor it into something sensible beyond that. Rupert On 1/24/07, Tomas Restrepo <[EMAIL PROTECTED]> wrote:
Hi Robert, > I think the java byte buffer is a very useful abstraction when writing > network apps - certainly much better than dealing with byte[] directly > - which was one of the reasons for taking it over to .NET. I had a > look but could not see anything directly comparable to it in .NET (but > that could just be my ignorance since I am not terribly familiar with > .NET). Well, in .NET usually most network apps I've been involved in basically deal with Streams and some form of stream readers and writers (either TextReader/Writer derived classes or something like a BinaryReader/Writer). I agree the model in the Java code seems interesting, and I agree manipulating a bunch of byte[] arrays ain't fun, so you'll get no discussion from me on that. That's why I'm proposing understanding the existing code better so we can clean it up a .NETify it a bit, I'm certainly not proposing a complete replacement with a different paradigm. Tomas Restrepo [EMAIL PROTECTED] http://www.winterdom.com/weblog/
