elein wrote:

>I am thinking too hard about this problem, I'm sure.
>
>node 1 has two children nodes 2 & 4
>node 2 has one child, node 3
>
>paths are set up between each possible pair.
>
>What should the listen look like?
>
>store listen (origin=1, receiver=2, provider=1);
>store listen (origin=2, receiver=1, provider=2);
>store listen (origin=1, receiver=4, provider=1);
>store listen (origin=4, receiver=1, provider=4);
>store listen (origin=2, receiver=3, provider=2);
>store listen (origin=3, receiver=2, provider=3);
>
>Should there also be:
>
>store listen (origin=1, receiver=3, provider=2);
>store listen (origin=3, receiver=1, provider=2);
>
>Thanks for your help.  I'm concerned I'm missing
>something basic.
>  
>
As soon as I get a few "round tuits," I'm going to see about generating 
a procedure and/or view that generates listen table contents based on 
the new 1.1 logic...

The base queries are in CVS HEAD; making it "pretty" is the next task...