Axel Dörfler wrote: >>What about using a static reply port here too ? It would be managed >>by the >>static lock, so it shouldn't run into concurrency problems. >>We would create it when BApplication calls InitData(), and destroy it >>when the >>BApplication dies. >>Or we could use the BApplication's reply port (as Adi suggested in >>the >>mentioned discussion). But I don't know if it's feasible. > > > I choose a simpler road for now, I just create a separate port on first > try, and it'll be alive as long as the application itself. > Since it doesn't lock the BApplication, and the reply is handled > directly (it doesn't go over the BApplication's message loop), we > cannot use the BApplication's reply port. Yes, we can. :-) Have a look through the code. This port is used for nothing after the initial app_server connection. bye, Adi.