[beepcore-ruby-discuss] Re: beepy

[Dan M. <dn...@po...>]

In a previous mail to the list that I didn't see because I wasn't 
subscribed (oops!), Jim Greer wrote:

>Any thoughts on an class/object model of the implementation?
>The beepy work (Python implementation) looks like a good start.

Is beepy the same thing as PyBEEP <http://pybeep.sourceforge.net/>? Gabe 
Wachob, the chief designer and instigator of PyBEEP is a friend of mine, 
and I've talked to him about various similarities. At the moment, I don't 
think PyBEEP is far enough along to look at as a potential anatomical BEEP 
core model, but I'll ask Gabe and get the straight dope.

I'm more interested in looking initially at beepcore-java because it's the 
BEEP core implementation that's had the most development done on it, and 
Huston Franklin is quick to fix bugs and explain complicated parts of the 
code. Gabe and I were recently writing a chapter on using BEEP to build 
peer-to-peer apps for a book project (which was unfortunately scrapped 
recently), and we selected beepcore-java because of the overall clarity, 
Huston's involvement and response time, and familiarity.

beepcore-tcl is potentially interesting because it attacks things from a 
realm which is a bit close to Ruby's domain: the scripting language 
approach. beepcore-tcl hasn't changed much from it's original inception as 
one of the original implementations of BEEP's predecessor, BXXP, but it may 
be worth looking at to learn from, especially in the case of how it 
leverages other libraries and code packages in Tcl to do things like XML 
parsing and what not. I certainly plan to use well-accepted and robust 
third party Ruby code to handle some of the more basic and/or esoteric 
things that aren't primarily related to the internals of BEEP wherever 
possible.


-- 
Dan Moniz <dn...@po...> [http://www.pobox.com/~dnm/]