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

[Justin W. <dae...@ei...>]

On Thu, 2008-10-02 at 09:38 -0700, Sam Roberts wrote:
> 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.

Hi Sam,

BEEPy is something I maintain in my spare time, along with other
projects, and it's not the highest priority one. Sorry, but that's what
you get with free stuff sometimes. I still have to pay my mortgage.

I appreciate that you took the time to send me the patches. I started
work on it, but it's not trivial to incorporate a big patch bundle like
that. I've always accepted small patches, but I've received precious
few.

The fact that the tests haven't been updated means that not only do I
have to incorporate the patch bundle, and inspect what it's changed to
ensure I'm ok with it, but I also have to update all the tests. This
increases the time it takes me to merge the code.

If you could update the tests to exercise the code you've changed, that
would go a long way to helping me incorporate your code.

Otherwise, it's just going to take a while. I appreciate that this
probably isn't what you wanted to hear.

Having said that, I may well have some increased ability to work on the
code in the near future, what with the holiday season approaching. Now
that I know it's important to you, I'll bump it up in priority.

-- 
Justin Warren <dae...@ei...>