[Pipet Devel] BL PL design documentation

[J.W. Bizzaro]

Jean-Marc Valin wrote:
> 
> Well, there is a real meaning between these grandma-mother-baby qualifiers, that
> would be lost with a BL1, BL2, BL3 scheme. You need only one grandma-BL (Jarl
> doesn't use the term, but in my mind it's the part responsible for "centralized
> distribution") to control a whole "piper program". You need many mother-BL's
> (one on each machine) for one grandma-BL. The same way, there are many baby-BL's
> for one mother-BL (many baby-BL's on each machine). If you don't like baby and
> grandma, what about super-BL (SBL), mother-BL (MBL) and child-BL (CBL)?

Then how about "1st Generation Broker" (G1B), "2nd Generation Broker" (G2B),
and "3rd Generation Broker" (G3B)?  "Generation" implies the same thing as
"Parent/Child".

Let me know if I've got this right:

  G1B (a.k.a. "Granny"):

    Part of the DL code base.  Spawns or communicates with
    multiple G2B's

  G2B (a.k.a. "Mommy"):

    The BL code base written by Jarl.  Spawns or communicates with
    multiple G3B's

  G3B (a.k.a. "Baby"):

    Part of the PL code base.

Jeff
-- 
J.W. Bizzaro                                           jeff at bioinformatics.org
Director, Bioinformatics.org: The Open Lab     http://bioinformatics.org/~jeff
"Injustice anywhere is a threat to justice everywhere."
               -- Martin Luther King, Jr.
--