Home » Modeling » EMF » [CDO] Invalidation notification for certain object types
| [CDO] Invalidation notification for certain object types [message #1009697] |
Fri, 15 February 2013 14:35  |
 Christophe Bouhier
Messages: 937
Registered: July 2009 |
Senior Member |
|
|
Hello there,
Currently we do not discriminate for which objects invalidations are
send. "All objects are created equal" so to say.
Does CDO support the capability to send invalidations for certain object
types?
I would like to limit invalidation events towards a UI Client, for
certain object, in other words have granular control of the invalidation
traffic being send from server to connected clients.
Could this actually be achieved by the CDOAdapter, or will all
invalidations be send over wire, regardless if a content adapter is
present? (Or is this actually the Subscription Policy?).
I think this answer will conclude my long lasting pursuit for the , well
hidden, CDO invalidation truth!
Cheers Christophe
"The cost of change: When things don't work, the CEO will change the
company, the manager will move around people, the programmer will commit
one line of code."
|
|
|
| Re: [CDO] Invalidation notification for certain object types [message #1009720 is a reply to message #1009697] |
Fri, 15 February 2013 15:26  |
|
Am 15.02.2013 15:35, schrieb Christophe Bouhier:
> Hello there,
>
> Currently we do not discriminate for which objects invalidations are send. "All objects are created equal" so to say.
>
> Does CDO support the capability to send invalidations for certain object types?
Not if by "types" you mean "EClasses".
> I would like to limit invalidation events towards a UI Client, for certain object, in other words have granular
> control of the invalidation traffic being send from server to connected clients.
>
> Could this actually be achieved by the CDOAdapter, or will all invalidations be send over wire, regardless if a
> content adapter is present? (Or is this actually the Subscription Policy?).
Yes, a CDOAdapterPolicy can be used with CDOView.Options.addChangeSubscriptionPolicy.
The CDOSession allows to disable pasive updates altogether: CDOSession.Options.setPassiveUpdatesEnabled/Mode.
>
> I think this answer will conclude my long lasting pursuit for the , well hidden, CDO invalidation truth!
It's all open source :P
Cheers
/Eike
----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper
Cheers
/Eike
----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper
|
|
|
| Re: [CDO] Invalidation notification for certain object types [message #1009769 is a reply to message #1009720] |
Fri, 15 February 2013 17:09 |
Christophe Bouhier
Messages: 937
Registered: July 2009 |
Senior Member |
|
|
On 15-02-13 16:26, Eike Stepper wrote:
> Am 15.02.2013 15:35, schrieb Christophe Bouhier:
>> Hello there,
>>
>> Currently we do not discriminate for which objects invalidations are
>> send. "All objects are created equal" so to say.
>>
>> Does CDO support the capability to send invalidations for certain
>> object types?
> Not if by "types" you mean "EClasses".
Yes EClasses or perhaps the name of a CDOResource so EFeatures as well?
>
>> I would like to limit invalidation events towards a UI Client, for
>> certain object, in other words have granular control of the
>> invalidation traffic being send from server to connected clients.
>>
>> Could this actually be achieved by the CDOAdapter, or will all
>> invalidations be send over wire, regardless if a content adapter is
>> present? (Or is this actually the Subscription Policy?).
> Yes, a CDOAdapterPolicy can be used with
> CDOView.Options.addChangeSubscriptionPolicy.
>
Just to be sure. Will the Change Subscription policy prevent any
invalidation communication when set to NONE for a CDOView?
If set to CDO, will it also
> The CDOSession allows to disable pasive updates altogether:
> CDOSession.Options.setPassiveUpdatesEnabled/Mode.
>
>>
>> I think this answer will conclude my long lasting pursuit for the ,
>> well hidden, CDO invalidation truth!
> It's all open source :P
>
Yeah right.. open nightmare you mean :P The problem is focus. I focus on
my domain and my application. If something is not working or whatever
underneath, I need to purge all this focus and switch to another world.
This is really hard to do...
> Cheers
> /Eike
>
> ----
> http://www.esc-net.de
> http://thegordian.blogspot.com
> http://twitter.com/eikestepper
>
>
|
|
|
| Re: [CDO] Invalidation notification for certain object types [message #1009773 is a reply to message #1009769] |
Fri, 15 February 2013 17:15 |
Christophe Bouhier
Messages: 937
Registered: July 2009 |
Senior Member |
|
|
On 15-02-13 18:09, Christophe Bouhier wrote:
> On 15-02-13 16:26, Eike Stepper wrote:
> > Am 15.02.2013 15:35, schrieb Christophe Bouhier:
> >> Hello there,
> >>
> >> Currently we do not discriminate for which objects invalidations are
> >> send. "All objects are created equal" so to say.
> >>
> >> Does CDO support the capability to send invalidations for certain
> >> object types?
> > Not if by "types" you mean "EClasses".
> Yes EClasses or perhaps the name of a CDOResource so EFeatures as well?
>
> >
> >> I would like to limit invalidation events towards a UI Client, for
> >> certain object, in other words have granular control of the
> >> invalidation traffic being send from server to connected clients.
> >>
> >> Could this actually be achieved by the CDOAdapter, or will all
> >> invalidations be send over wire, regardless if a content adapter is
> >> present? (Or is this actually the Subscription Policy?).
> > Yes, a CDOAdapterPolicy can be used with
> > CDOView.Options.addChangeSubscriptionPolicy.
> >
> Just to be sure. Will the Change Subscription policy prevent any
> invalidation communication when set to NONE for a CDOView?
>
> If set to CDO, will it also
Oops, unfinished sentence here.
One more clarification. If the Change Subscription Policy is set to CDO,
will there be communication, for object which don't have a a CDOAdapter
installed?
I think the answer is yest, otherwise would never have received CDO
invalidation events...
>
> > The CDOSession allows to disable pasive updates altogether:
> > CDOSession.Options.setPassiveUpdatesEnabled/Mode.
> >
> >>
> >> I think this answer will conclude my long lasting pursuit for the ,
> >> well hidden, CDO invalidation truth!
> > It's all open source :P
> >
> Yeah right.. open nightmare you mean :P The problem is focus. I focus on
> my domain and my application. If something is not working or whatever
> underneath, I need to purge all this focus and switch to another world.
> This is really hard to do...
>
>
> > Cheers
> > /Eike
> >
> > ----
> > http://www.esc-net.de
> > http://thegordian.blogspot.com
> > http://twitter.com/eikestepper
> >
> >
|
|
|
| Re: [CDO] Invalidation notification for certain object types [message #1009824 is a reply to message #1009773] |
Fri, 15 February 2013 19:48 |
|
Am 15.02.2013 18:15, schrieb Christophe Bouhier:
> On 15-02-13 18:09, Christophe Bouhier wrote:
>> On 15-02-13 16:26, Eike Stepper wrote:
>> > Am 15.02.2013 15:35, schrieb Christophe Bouhier:
>> >> Hello there,
>> >>
>> >> Currently we do not discriminate for which objects invalidations are
>> >> send. "All objects are created equal" so to say.
>> >>
>> >> Does CDO support the capability to send invalidations for certain
>> >> object types?
>> > Not if by "types" you mean "EClasses".
>> Yes EClasses or perhaps the name of a CDOResource so EFeatures as well?
>>
>> >
>> >> I would like to limit invalidation events towards a UI Client, for
>> >> certain object, in other words have granular control of the
>> >> invalidation traffic being send from server to connected clients.
>> >>
>> >> Could this actually be achieved by the CDOAdapter, or will all
>> >> invalidations be send over wire, regardless if a content adapter is
>> >> present? (Or is this actually the Subscription Policy?).
>> > Yes, a CDOAdapterPolicy can be used with
>> > CDOView.Options.addChangeSubscriptionPolicy.
>> >
>> Just to be sure. Will the Change Subscription policy prevent any
>> invalidation communication when set to NONE for a CDOView?
>>
>> If set to CDO, will it also
>
> Oops, unfinished sentence here.
> One more clarification. If the Change Subscription Policy is set to CDO, will there be communication, for object which
> don't have a a CDOAdapter installed?
>
> I think the answer is yest, otherwise would never have received CDO invalidation events...
Exactly. The only way to stop server pushes is to disable passive updates in the session options.
Cheers
/Eike
----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper
>
>
>>
>> > The CDOSession allows to disable pasive updates altogether:
>> > CDOSession.Options.setPassiveUpdatesEnabled/Mode.
>> >
>> >>
>> >> I think this answer will conclude my long lasting pursuit for the ,
>> >> well hidden, CDO invalidation truth!
>> > It's all open source :P
>> >
>> Yeah right.. open nightmare you mean :P The problem is focus. I focus on
>> my domain and my application. If something is not working or whatever
>> underneath, I need to purge all this focus and switch to another world.
>> This is really hard to do...
>>
>>
>> > Cheers
>> > /Eike
>> >
>> > ----
>> > http://www.esc-net.de
>> > http://thegordian.blogspot.com
>> > http://twitter.com/eikestepper
>> >
>> >
>
Cheers
/Eike
----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper
|
|
|
Goto Forum:
Current Time: Fri Apr 26 13:06:19 GMT 2024
Powered by FUDForum. Page generated in 0.03108 seconds |
] 
Search
Help
Register
Login
Home
