Hello Michael,

MA> cool.

;-)

MA> Yes, it should be possible to have multiple contract instances of the
MA> same contract type in the same kernel. Are you using the C++ or JAVA kernel?

I'm using the JAVA kernel.

Several clients can subscribe to informations with there own specific
updaterate (millisec). Now, the contract compare the expected
updaterate with the measured updaterate and the delegate adapt the
callback, if the are different.

The creation of one delegate for each client-callback object works,
but the instantiated Qoskets in the delegates use the same contract
(every new created Qosket overides the old contract in the kernel with
a new one). I need one contract for each delegate.

A further problem for me is the publicity of local SysConds in contracts. Is
there another way to access to this SysConds in addition to probed
SysConds?


the contract:

contract UpdaterateMonitorContract (
syscond quo::ValueSC quo_sc::ValueSCImpl updateRate
//created in the Qosket with one ID for every delegate ... ??
)
{
syscond probe bqosket::UpdaterateQosket::UpdaterateProbe
timeDiff("QuotationTime");

region Expected (true) { }

region Unexpected ((long long)timeDiff != (long long)updateRate) { }
};



Sven

--
[To unsubscribe to this list send an email to "majdart@..."
with the following text in the BODY of the message "unsubscribe quo-users"]