- 1 Evaluation Stack Interface
- 2 Stack Filter Interface
- 3 Cache Data Interface
- 4 Cache Service
- 4.1 (15) SDK: ILxCacheService interface
- 4.2 (16) SDK: ILxCacheService interface
- 4.3 (17) SDK: ILxCacheService interface
- 4.4 (18) SDK: ILxCacheService interface
- 4.5 (19) SDK: ILxCacheService interface
- 4.6 (20) SDK: ILxCacheService interface
- 4.7 (21) SDK: Declarations
- 4.8 (22) User Service Class: CacheService method
- 4.9 (23) PY: CacheService method
Evaluation Stack Interface
(1) SDK: ILxEvaluationStack interface
(2) SDK: Declarations
#define LXu_EVALUATIONSTACK "47F3BF05-B64A-49D9-A2C1-08B0D36AB787"
(3) User Class: EvaluationStack method
Empty EvaluationStack Python user class.
(4) PY: EvaluationStack method
Stack Filter Interface
Stacks are made of filters. Here we define an interface that is common to all filter types:
|Returns the filter type. This is a string that identifies the type of the filter, and will be used to determine if two filter objects can be compared. If you don't want your Compare() method called with all kinds of other filters you should make sure this string is unique.|
|Compares to another filter and returns LXiSTACK_IDENTICAL if the results of these filters would be the same, LXiSTACK_COMPATIBLE if the output of the other filter can be converted to this one's, or LXiSTACK_DIFFERENT if they are irreconcilable.|
|If this filter is unused but found to be compatible with another of the same type, the Convert() method will be called to convert this one to match the new desired form. The filter should remember the jist of the differences and update destination object when applied.|
|This is expected to return an identifier that identifies this filter in an evaluation stack.|
(5) SDK: ILxStackFilter interface
(6) SDK: Declarations
(7) User Class: StackFilter method
Empty StackFilter Python user class.
(8) PY: StackFilter method
ILxStackFilter1 (Legacy Interface)
(9) SDK: ILxStackFilter1 interface
(10) SDK: Declarations
#define LXu_STACKFILTER1 "B79CF5D3-C630-401B-82A5-AD866BC05B6F"
Cache Data Interface
Items stored in the cache are simple COM objects with a single method - the Size method. Size is provided by the client so that the cache system may effectively manage memory since it has no knowledge of the data itself.
|The Size method is used to allow the cache system to query the CacheData object to determine its size for memory managemnt purposes and only memory management purposes. Calling this function does no allocation or anything other than reporting how much memory this object uses.|
(11) SDK: ILxCacheData interface
(12) SDK: Declarations
#define LXu_CACHEDATA "7561D111-72BD-4C0C-9E2D-9268A0EC30C2"
(13) User Class: CacheData method
Empty CacheData Python user class.
(14) PY: CacheData method
The Cache Service is basically the above Cache functions wrapped into a COM object and exported to SDK.
|Clients are added to the cache by simply registering their name. Success means the new client has been created and initialized. Failure means the client already exists.|
|Frees all of the data objects stored in the named cache. Note that the data objects stored in the client will just have XObjectRelease called on them.|
|Passes back by reference the object in the named cache for the given key. Returns result code.|
|Adds the data object to the named cache.|
|Frees (XObjectReleases) all of the data in the named cache.|
(15) SDK: ILxCacheService interface
(16) SDK: ILxCacheService interface
(17) SDK: ILxCacheService interface
(18) SDK: ILxCacheService interface
(19) SDK: ILxCacheService interface
(20) SDK: ILxCacheService interface
(21) SDK: Declarations
#define LXu_CACHESERVICE "6BB353D3-179A-477A-AC23-946DECB45A37"
(22) User Service Class: CacheService method
Empty CacheData Python user class.
(23) PY: CacheService method