Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 15 Next »

Documentation Incomplete

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

  1. 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)
  2. 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

application

-

objectbroker

-

-

typename

-

-

-

objectpool

(structure, keyed by OBJECTID, of content item structures)

-

-

-

objectpool

stobj

-

-

-

objectpool

stwebskins(structure keyed by template name and/or url hash

-

-

-

aObjects

(manage object pooling by FIFO)

-

-

-

maxobjects

(maximum number of objects to cache)
  • No labels