Hi Piper People, As promised I made an overview of the structure of the BL nodes that connect the DL to the PL. This configuration is realised during boot-up of the BL, and will always be there. Making it configurable or optional can be done, but seems to of no interest to Piper ;) Note that all the parts between the DL and PL on the drawing are one-and-the-same process, the BL. The sensors, visuals and collectors are dynamic loadable modules, that's why I did draw them seperate from the pipeline. Also take notice of the way the communication between the DL and PL is setup. Communications back and forth go through the pipeline, so they are authorized, scheduled, etc. Also is it in the nature that the DL and PL do not need to be one the same machine. Neither do the possible other instances. When there're no complains, no mistakes or unclear stuff, can you put this on the piper site Jeff? Thnx ;) jarl -------------- next part -------------- A non-text attachment was scrubbed... Name: DL2PL.eps Type: application/postscript Size: 25225 bytes Desc: not available Url : http://bioinformatics.org/pipermail/pipet-users/attachments/20010113/a8c5384b/DL2PL.eps -------------- next part -------------- A non-text attachment was scrubbed... Name: DL2PL.png Type: image/png Size: 21542 bytes Desc: not available Url : http://bioinformatics.org/pipermail/pipet-users/attachments/20010113/a8c5384b/DL2PL.png