• Following no one
  • Nothing Unseen
  • Someone Random
  • Everyone
  • Events
 

John Palmieri   -   Follow Person   Add Another Site   Edit
J5    gnome:j5    johnp    John (J5) Palmieri    fedora:johnp   
Flickr photos


identi.ca
anyone in for skiing at catamount this sunday? 18 days ago
just voted in the MA senate special election. Make sure to get to the polls by 8pm 20 days ago
MA residents. Jan. 19th is the special election to fill Edward Kennedy's vacant Senate seat. Polls are close so please vote! 24 days ago
J5's Blog
The Quest for Python 3   5 days ago

Well, I’ve gone and done it. Thanks to David Malcolm’s excellent 2to3c tool and some hand wrangling with PyUnicode objects I was able to get D-Bus Python compiling and working on Python 3. Grab the patch and start testing it out.

I’ve also tested this under Python 2.6 but it would be nice to see if it also works under Python versions < 2.6 since 2.6 has a couple of compatibility layers built in.

[read this post in: ar de es fr it ja ko pt ru zh-CN ]

kamaloka-js 0.9.0 released   11 days ago

I am proud to announce the second release of the kamaloka-js AMQP bindings. This release brings with it a high level API modeled after the new Sender/Receiver and addressing API’s being developed in the Qpid project. It is intended to bridge the gap between the 0.10 protocol and the upcoming 1.0 protocol. I have also simplified the code base and improved the code generator. Because we are getting so close to implementing the complete 0.10 protocol spec, we have bumped the version to the 0.9.x series to indicate a redefined focus on stabilizing the current code base. You will notice significant API changes from 0.1.0 to 0.9.0. We hope to not have to make too many more changes during the current cycle of development and hope to get a 0.10 version out once we have completed coverage of the entire spec.

Some of the highlights of this release are:

Flattening the model   12 days ago

In my quest for cleaner code in Kamaloka-js I have been working on simplifying the dispatch model.  AMQP has some interesting features built into it to facilitate real-time functionality along with message prioritization.  To accomplish this messages can be sent on different queues and tracks, and also be broken up into segments which can be further broken up into frames.

Frames

Frames are the basic building blocks of the AMQP data stream.  They contain complete headers that describe queue, track and segment that is currently being constructed.  The payload of a frame (the segment being built) can be broken up into arbitrary sized byte arrays which are then reassembled based on the channel and track they are sent on.  In this way applications with memory constraints can request that frames be no bigger than what the application can fit in memory.  A typical frame header looks something like:


Learn about this site | Contact
API | Source Code
© 2008 Christopher Blizzard