> Ok, have a AIL (I'll just adopt the naming) as a seperate module > (ofcourse with CORBA inferface(s)) is obvious to me. But putting it > inbetween the DL and BL doesn't seem a good design to me. Neither > intergrating it into the BL. The way I see a GP engine fit into piper is > as a general support module. Something all layers could make use of. > Sort off a base class for the total monster we call Piper ;) Makes sense. In fact, the more I think about it it seems that the AIL could be used for a lot of things in all layers. Maybe it makes sense to integrate some sort of a switchbox function into the BL that allows the BL to chain in the AIL everywhere where it is needed. Maybe it makes even more sense to split up the AIL in a number of blocks ( rule based, genetic etc. ) to enhance its configurability and consequently its versatility. ======================================================================= "It was hell. They knew it. Karl-Max Wagner But they called it karlmax at oberland.net W-I-N-D-O-Z-E" ham radio: DB8CO *********Member of No Code International********* ***********Visit http://www.nocode.org*********** ********Membership Number NCI-2563-DB8CO********* _ / / (_)__ __ ____ __ / /__/ / _ \/ // /\ \/ / . . . t h e c h o i c e o f a /____/_/_//_/\_,_/ /_/\_\ G N U g e n e r a t i o n . . "Et ceterum censeo ut Microsoftem delendum esse" (Cato, adapted) "Quo usque tandem abutere nostra patientia ?" (Cicero, original) =======================================================================