I'm sorry to say that I don't have anything useful to add, except to say that I've been interested in making proton python asynchio compatible for some time. To a first look qpid bow looks like the approach I would have taken, but it seems to be based on a very old version of python qpid proton, so this might be the reason it doesn't work!
Hope this is at least a little helpful. Andrew On Wed, Dec 18, 2024 at 11:00 AM Steve Huston <shus...@riverace.com> wrote: > I am working on a python application that will allow multiple plug-in > modules that add different features and ways to request things, all by > various network paths. My intention is to drive it with python asyncio, and > each plugin piggybacks on that by using asyncio. > > The first plugin is to use AMQP messaging so I started with proton, which > works fabulously when following the examples. However, it doesn't follow > the asyncio framework so I'm trying to work that out. > > I tried qpid-bow (https://github.com/Bynder/qpid-bow) that claims to > integrate the proton reactor with asyncio. I have been unable to get it to > work past the initial batch of events to connect (or attempt to connect) to > a broker. > > My next idea was to run the proton-based plugin's work in another thread > and tie that thread's completion into asyncio's loop, leaving proton > reactor to run freely. I'm having trouble there too. I added a simple > http-based plugin just to have more than one and they both start but as > soon as proton gets to so anything, the http plugin never gets to run again. > > There's still a good chance I have something fundamentally wrong with the > way I'm running asyncio, but I'm interested in any advice or experience > from people here who have worked with asyncio and proton - should this be > able to work? > > Thanks, > -Steve Huston > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org > For additional commands, e-mail: users-h...@qpid.apache.org > >
