[Ace-users] Re: [ciao-users] Question about creation of facet
servant and executor
William R. Otte
wotte at dre.vanderbilt.edu
Thu Aug 16 16:28:35 CDT 2007
Hi Abdul -
To follow up, I found the following nugget on page 14 of 06-04-01
> In general, a component instance shall be prepared to return
object references for facets throughout the instance’s life
> cycle. A component implementation may, as part of its advertised
behavior, return a nil object reference as the result of
> a provide_<name> operation.
This certainly suggests that the intuitive behavior (ie, servant
queries the executor each time) is the behavior mandated by the spec.
On Aug 16, 2007, at 4:00 PM, Sowayan, Abdullah (N-DUA) wrote:
> Hi Will,
>> -----Original Message-----
>> From: ciao-users-bounces at cse.wustl.edu [mailto:ciao-users-
>> bounces at cse.wustl.edu] On Behalf Of William R. Otte
>> Sent: Thursday, August 16, 2007 4:57 PM
>> To: CIAO Users Mailing List
>> Subject: Re: [ciao-users] Question about creation of facet servant
>> Hi Santos -
>> On Aug 16, 2007, at 3:42 PM, santos . wrote:
>>> I would appreciatte if you can help me clarifying some doubts about
>>> facet objects behavior. The get_facet_name in the component
>>> executor returns to the container an facet executor. If in my
>>> component executor I have a method implemented like that:
>>> ::App::CCM_IFooFacet_ptr Foo_exec_i::get_foo_facet ()
>>> // Your code here.
>>> return ( new IFooFacet_exec_i () );
>>> Will I have two diferent servants for the same facet? Will the
>>> reference received by the Client1 receptacle point to a different
>>> object than that received by Client2? Will it be created one
>>> IfooFacet_exec_i executor for each connection?
>> Right now, the servant code caches the first result of get_foo_facet,
>> so each connection will be served by a common facet executor.
> Hmmm, that seems counter intuitive to me. Is this spec compliant or
> CIAO-specific behavior?
> ciao-users mailing list
> ciao-users at mail.cse.wustl.edu
More information about the Ace-users