| Warning | ||
|---|---|---|
| ||
These are notes during the beta cycle only and are not complete – examples may not reflect best practice with respect to the final release of the 4.0 code base. |
Basic process flow
- on fourq.getData() calls
- check typename.objectpool for UUID
- if present
- return struct
- if not,
- make dbgateway call
- check if room in objectpool
- purge/update aobjects FIFO list as required
- update objectpool with object struct
- return struct
- update cache stats (no cache stats implemented at this time 20070505)
- if present
- check typename.objectpool for UUID
- return object struct to content type call exactly as per original
Object Broker Webtop Report
You can check which content types have been activated for the object broker by running the Objectbroker Report in the webtop Admin section. This should indicate those content types using the objectbroker, there maximum threshold and the current number of objects in the broker.
In memory structure of object broker
...
- check typename.objectpool for UUID
- if present
- return struct
- if not,
- make dbgateway call
- check if room in objectpool
- purge/update aobjects FIFO list as required
- update objectpool with object struct
- return struct
- update cache stats
- if present
...
application | |||||
- | objectbroker | ||||
- | - | typename | |||
- | - | - | objectpool | (structure, keyed by OBJECTID, of content item structures) | |
- | - | - | aObjects | (manage object pooling by FIFO)objectpool | stobj |
- | - | - | cachestats | -objectpool | stwebskins(structure keyed by template name and/or url hash |
- | - | - | cachehits | -aObjects | (manage object pooling by FIFO) |
- | - | - | cachepops |
Basic process flow
maxobjects | (maximum number of objects to cache) |