|
|||||||||
| PREV CLASS NEXT CLASS | FRAMES NO FRAMES | ||||||||
| SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD | ||||||||
public interface SimpleVariablePipelineIF
Simple interface implemented by several stages in the Web distributed-variable-handling pipeline. The pipeline stages that implement this may well implement other interfaces in parallel to provide richer and more efficient cacheing, etc.
| Method Summary | |
|---|---|
void |
syncVariables(boolean force)
Synchronise variables with upstream values. |
| Methods inherited from interface org.hd.d.pg2k.svrCore.vars.BasicVarMgrInterface |
|---|
getEventValue, getEventValues, getVariable, getVariables, setVariable, setVariables |
| Method Detail |
|---|
void syncVariables(boolean force)
throws java.io.IOException
When called with force==true, this acts like a full "memory barrier", flushing all write-cached items downstream immediately and afterwards getting the value of all upstream values with getVariables(-1), but may be expensive in terms of CPU or bandwidth, so use sparingly.
When called with force==false, this incrementally flushes outstanding writes and will then fetch all, or only new, values from upstream, so is potentially much less resource-intensive. In particular, this does not propagate the sync() upstream.
In any case, it is rarely the right thing for a casual user to call this as it may be very expensive.
force - if true, this will force a full write flush,
a full sync upstream,
then full read with getVariables(-1),
to get the effect of a full "barrier";
otherwise, in general, a more incremental and non-propagating
mode is used which still does a write flush but may chose
to do a partial read of "new" upstream values
java.io.IOException - if one is received from upstream
|
DHD Multimedia Gallery V1.53.0 | ||||||||
| PREV CLASS NEXT CLASS | FRAMES NO FRAMES | ||||||||
| SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD | ||||||||