[fnorb] Fnorb implementation of POA : when expected ?

Martin von Loewis loewis at informatik.hu-berlin.de
Tue Aug 29 11:28:31 EDT 2000


> I suspect that the main reason for changing the BOA to POA, is the
> fact that under the BOA, one needs to create a new implementation
> for every new object created.

I can't speak on plans to build a POA into Fnorb, but the above
statement is certainly not true. Or, perhaps, I misread the statement:
you don't need to write a new implementation class; you can certainly
instantiate the same implementation class as many times as you want.

I belive with Fnorb, you can also use the same implementation object
(servant, in POA speak) for many CORBA object references, by
activating it multiple times.

With the POA, you'd get that, and a number of additional features
(like servant creation on-the-fly, e.g. only when a request comes in).

> MHO about some new operators :
> Today I found myself writing something like this :
> 
> ObjectFactoryImpl.ObjCnt = ObjectFactoryImpl.ObjCnt + 1
> 
> (Incrementing a static class member by one)
> 
> So, adding operators like +=, ++, etc, seems to me an improvement

Indeed, += is an improvement. Please note that ++ was not added...

Regards,
Martin




More information about the Python-list mailing list