[Pipet Devel] Baby-BL implementation

Brad Chapman chapmanb at arches.uga.edu
Mon Sep 11 17:08:17 EDT 2000

Hey all;

Apologies in advance for being late on responding to all of this. I have
just now come to some understanding of what is going on, and didn't want
to respond when I was so confused. Sorry for being so slow on coming to
grips with this!

Jean-Marc wrote:
>  I've attached how I see the Baby-BL (which links to the PL) being
>  implemented.
>  Comments are welcome.

This makes a lot of sense and seems very practical:

1. Fire up a CORBA server in the BBL and wait for calls from the MBL.

2. Call getOutput upon demand from the MBL to run a network (or
subsection of a network).

3. Call fetchInput upon demand from the PL to get input from a particular
node that may be remotely located.

So, if I am with you so far, this just leads to a couple of questions:

1. It seems like this requires that the MBL be smart enough to know that
it needs to split a network at display nodes, so that it can have access
to the results that need to be displayed. So if we we had Jean-Marc's
famous A->(B->C)->D network and say C were a viewer that needed to get
results, then the MBL would have to know to split the network here and
call getOutput on C (before calling on D), so that is could have the
output for display. Is this right, or am I way off base?

2. I'm not sure how the Overflow *Probe will work under this system. Am I
missing something basic?

Otherwise it looks great. You and Jarl seem to really have a good system
down here. Please let me know how you'd like me to help with the
implementation details of the BBL stuff (if at all!) and I'll be more
than happy to do some coding.


More information about the Pipet-Devel mailing list