[beepy-devel] status of beepy, still can't connect to any other beep imps, AFAIK

[Sam R. <sro...@wu...>]

Justin, have you tried to use beepy to connect to any other BEEP
implementations yet?

Its broken SEQ number handling prevents interop with beep4j and vortex,
for example.

Those bugs are among the ones we fixed.

Sorry the patch sucked, but to get good patches, you need to regularly
accept and integrate small patches, or else fix them yourself. Btw, it
deliberately modified the API, the old API had conceptual problems,
so the tests will need to rewritten.

Since our last email, we'll also fixed some problems that caused beepy,
already not very fast, to slow to a crawl on large messages and suck
100% CPU, and probably various other stuff.

We don't want to maintain this fork ourselves indefinitely, so we'll
probably rename our code and post a new project to sourceforge some time
unless these changes get integrated.

We're happy to answer questions about any areas of the patch we sent,
but I never heard back from you.

Cheers,
Sam