Cache Xbase++ Reference Documentation

Cache

Current Version: 11.6.0

Chilkat.Cache

Store, retrieve, expire, and clean up cached text or binary data on disk.

Chilkat.Cache is a disk-based cache class for storing and retrieving text or binary items by unique key. It provides configurable cache roots, optional multi-level directory layout, expiration metadata, ETag metadata, cache lookup, fetch-status properties, expiration updates, and cleanup methods for deleting individual items, expired items, older items, or the entire cache.

Key-based storage

Store and retrieve cached items by unique key, without the application needing to manage the underlying cache filenames directly.

Text and binary data

Cache strings, byte data, files, or Chilkat buffer objects depending on the data form used by the application.

Expiration control

Associate cached items with expiration times, update expiration metadata, and check whether cached content is still usable.

ETag metadata

Store and retrieve ETag values for workflows that need HTTP-style cache validation or conditional re-fetch logic.

Configurable layout

Choose the cache root directory and use an optional multi-level directory structure to avoid too many files in a single folder.

Cleanup operations

Delete a single cached item, remove expired items, remove older items, or clear the entire cache when needed.

Common pattern: Configure the cache root, choose the key used to identify each item, check whether a valid cached copy exists, fetch or regenerate the content when needed, store it with expiration and optional ETag metadata, and periodically clean up expired or old cached items.

Object Creation

LOCAL oCache
oCache := CreateObject("Chilkat.Cache")

// ... use oCache ...

oCache:destroy()

Xbase++ uses the Chilkat ActiveX through the automation object returned by CreateObject(); properties and methods are accessed with the send operator (oHttp:ConnectTimeout := 30, oHttp:Download(cUrl, cPath)), and :destroy() releases the object. Register the Chilkat ActiveX matching the bitness of your Xbase++ application. To bind to a specific major version of Chilkat, append the major version number to the ProgID, such as CreateObject("Chilkat.Cache.11") for Chilkat v11.*.*.

Boolean properties, arguments and return values are integers in the ActiveX: pass 1 or 0, and test a method's success with == 1. A method that fails to return an object returns NIL. Objects returned by methods (such as an HttpResponse or JsonObject) are automation objects too and should likewise be released with :destroy(). Methods and properties that pass or return raw byte arrays are not shown on this page; use the BinData-based alternatives (methods ending in Bd) or the base64 / hex string-encoded variants instead.

Properties

DebugLogFilePath
oCache:DebugLogFilePath // Character

If set to a file path, this property logs the LastErrorText of each Chilkat method or property call to the specified file. This logging helps identify the context and history of Chilkat calls leading up to any crash or hang, aiding in debugging.

Enabling the VerboseLogging property provides more detailed information. This property is mainly used for debugging rare instances where a Chilkat method call causes a hang or crash, which should generally not happen.

Possible causes of hangs include:

  • A timeout property set to 0, indicating an infinite timeout.
  • A hang occurring within an event callback in the application code.
  • An internal bug in the Chilkat code causing the hang.

More Information and Examples
top
LastErrorHtml
oCache:LastErrorHtml // Character (read-only)

Provides HTML-formatted information about the last called method or property. If a method call fails or behaves unexpectedly, check this property for details. Note that information is available regardless of the method call's success.

top
LastErrorText
oCache:LastErrorText // Character (read-only)

Provides plain text information about the last called method or property. If a method call fails or behaves unexpectedly, check this property for details. Note that information is available regardless of the method call's success.

top
LastErrorXml
oCache:LastErrorXml // Character (read-only)

Provides XML-formatted information about the last called method or property. If a method call fails or behaves unexpectedly, check this property for details. Note that information is available regardless of the method call's success.

top
LastEtagFetched
oCache:LastEtagFetched // Character (read-only)

Returns the ETag metadata associated with the most recently fetched cache item. An empty string means that the fetched item has no stored ETag.

Read after a fetch: This property describes the item returned by the most recent successful fetch operation, such as FetchBd, FetchSb, or FetchText.
ETags are opaque metadata: The cache stores and returns the string but does not interpret it. Applications commonly use an HTTP ETag with conditional requests such as If-None-Match.

top
LastExpirationFetchedStr
oCache:LastExpirationFetchedStr // Character (read-only)

Returns the expiration date and time stored for the most recently fetched cache item, formatted as an RFC 822-style Internet date. An empty string represents an item with no expiration date.

Expiration is metadata: Fetching an expired item is still possible. Read LastHitExpired after the fetch to determine whether the returned entry is stale.

top
LastHitExpired
oCache:LastHitExpired // Numeric (read-only)

Returns 1 when the expiration time of the most recently fetched item is earlier than the current system date and time; otherwise returns 0.

Expired does not mean deleted: Expiration marks an entry as stale. The file remains in the cache until it is replaced or removed by methods such as DeleteAllExpired or DeleteFromCache.

top
LastKeyFetched
oCache:LastKeyFetched // Character (read-only)

Returns the application-defined key associated with the most recently fetched cache item.

Keys are not limited to URLs: A canonicalized URL is a common key for cached web content, but any unique string may be used. Reusing a key causes a save operation to replace the existing item for that key.

top
LastMethodSuccess
oCache:LastMethodSuccess // Numeric

Indicates the success or failure of the most recent method call: 1 means success, 0 means failure. This property remains unchanged by property setters or getters. This method is present to address challenges in checking for null or Nothing returns in certain programming languages. Note: This property does not apply to methods that return integer values or to boolean-returning methods where the boolean does not indicate success or failure.

top
LastStringResult
oCache:LastStringResult // Character (read-only)

In SQL Server stored procedures, this property holds the string return value of the most recent method call that returns a string. It is accessible only when Chilkat.Global.KeepStringResult is set to TRUE. SQL Server has limitations on string lengths returned from methods and properties, but temp tables can be used to access large strings.

top
LastStringResultLen
oCache:LastStringResultLen // Numeric (read-only)

The length, in characters, of the string contained in the LastStringResult property.

top
Level
oCache:Level // Numeric

Gets or sets the number of directory levels used beneath each cache root. Valid values are 0, 1, and 2.

ValueDirectory layout
0All cache files are stored directly in the cache root.
1Files are distributed among 256 first-level directories named 0 through 255.
2Files are distributed through two levels of 256 directories, allowing as many as 65,536 leaf directories per root.
Configure before use: Use the same level when reopening an existing cache. Changing the layout does not reorganize previously stored files and can prevent the object from locating them through their keys.

top
NumRoots
oCache:NumRoots // Numeric (read-only)

Returns the number of cache-root directories that have been registered by calling AddRoot.

Multiple roots: A cache may span more than one directory or storage device. Configure the same root set when reopening a persistent cache so previously stored items remain discoverable.

top
VerboseLogging
oCache:VerboseLogging // Numeric

If set to 1, then the contents of LastErrorText (or LastErrorXml, or LastErrorHtml) may contain more verbose information. The default value is 0. Verbose logging should only be used for debugging. The potentially large quantity of logged information may adversely affect peformance.

top
Version
oCache:Version // Character (read-only)

Version of the component/library, such as "10.1.0"

More Information and Examples
top

Methods

AddRoot
oCache:AddRoot(cPath)

Adds path as a root directory for the disk cache. Call this method once for each root that should participate in the cache.

For example, a cache distributed across D:\cacheRoot, E:\cacheRoot, and F:\cacheRoot is configured by calling this method three times.

Use dedicated writable directories: Cache cleanup methods can delete cache files beneath every configured root. Do not mix unrelated application files into a cache root.
Persistent configuration: Recreate the same roots and Level setting before accessing a cache created by an earlier process or application run.
top
DeleteAll
nResult := oCache:DeleteAll() // returns Numeric

Deletes every cache item from all configured roots and returns the number of cache files removed. Multi-level subdirectories are retained.

Destructive operation: This cannot be limited to a key prefix or reversed. Use cache roots dedicated to Chilkat cache data.
top
DeleteAllExpired
nResult := oCache:DeleteAllExpired() // returns Numeric

Deletes all cache items whose stored expiration time is earlier than the current system time and returns the number of files removed.

Non-expiring entries remain: Items saved without an expiration date are not removed by this method.
top
DeleteFromCache
nSuccess := oCache:DeleteFromCache(cKey) // returns Numeric (1/0)

Deletes the cache item identified by key.

Return valueMeaning
1The item was deleted, or no item existed for the key.
0The item exists but could not be deleted, for example because of a filesystem permission or sharing error.
Idempotent deletion: A missing key is not treated as an error, which makes it safe to call this method when the application merely wants to ensure that an item is absent.

Returns 1 for success, 0 for failure.

top
DeleteOlderDt
nResult := oCache:DeleteOlderDt(oDateTime) // returns Numeric

Deletes cache items older than the cutoff date and time supplied in dateTime.

Returns the number of cache files deleted, or -1 if an error occurs.

Different from expiration cleanup: Use DeleteAllExpired when the decision should be based specifically on each item's expiration metadata.
top
DeleteOlderStr
nResult := oCache:DeleteOlderStr(cDateTimeStr) // returns Numeric

Deletes cache items older than the cutoff date and time supplied in dateTimeStr as an RFC 822-style Internet date string.

Returns the number of cache files deleted, or -1 if an error occurs.

Date format: A typical value is Mon, 03 Aug 2026 12:00:00 GMT. Use DeleteOlderDt when the cutoff is already available as a CkDateTime.
top
FetchBd
nSuccess := oCache:FetchBd(cKey, oBd) // returns Numeric (1/0)
Introduced in version 9.5.0.91

Retrieves the binary item identified by key and loads its bytes into the BinData object supplied in bd.

The key is application-defined, may contain any characters, and must uniquely identify the intended item.

Check the return value: Use the destination only when this method returns 1. A failed lookup or filesystem error returns 0.
Freshness: A successful fetch may return an expired item. Read LastHitExpired immediately afterward when stale data must not be used.

Returns 1 for success, 0 for failure.

top
FetchSb
nSuccess := oCache:FetchSb(cKey, oSb) // returns Numeric (1/0)
Introduced in version 9.5.0.91

Retrieves the text item identified by key and loads its content into the StringBuilder supplied in sb.

The key is application-defined, may contain any characters, and must uniquely identify the intended item.

Check the return value: Use the destination only when this method returns 1. A failed lookup or filesystem error returns 0.
Freshness: A successful fetch may return an expired item. Read LastHitExpired immediately afterward when stale data must not be used.

Returns 1 for success, 0 for failure.

top
FetchText
cResult := oCache:FetchText(cKey) // returns Character

Retrieves the text item identified by key and returns its string content.

The key is application-defined, may contain any characters, and must uniquely identify the intended item.

Freshness is separate: A successful fetch can return an expired entry. Read LastHitExpired immediately afterward when the application requires only fresh data.

Returns NIL on failure

top
GetEtag
cResult := oCache:GetEtag(cKey) // returns Character

Returns the ETag metadata stored with the cache item identified by key.

Opaque value: Chilkat does not parse or validate the ETag. An application may store any auxiliary string here, although HTTP entity tags are the common use case.

Returns NIL on failure

top
GetExpirationStr
cResult := oCache:GetExpirationStr(cUrl) // returns Character

Returns the expiration date and time stored for the item identified by url, formatted as an RFC 822-style Internet date string.

Argument name: Some language bindings name url url for historical reasons. It is the cache key and does not need to be a URL.
No-expiration entries: An empty stored expiration represents an item that does not expire automatically.

Returns NIL on failure

top
GetFilename
cResult := oCache:GetFilename(cKey) // returns Character

Returns the absolute filesystem path of the cache file associated with key.

Implementation detail: Treat the returned path as diagnostic information. Applications should normally read, update, and delete entries through the Cache API rather than modifying cache files directly.

Returns NIL on failure

top
GetRoot
cResult := oCache:GetRoot(nIndex) // returns Character

Returns the directory path of the cache root at zero-based index. Valid indexes range from 0 through NumRoots - 1.

Returns NIL on failure

top
IsCached
nSuccess := oCache:IsCached(cKey) // returns Numeric (1/0)

Returns 1 if an item exists for key, or 0 if the key is not present.

Presence is not freshness: This method does not imply that the entry is unexpired. Fetch the item and examine LastHitExpired, or read its expiration metadata, when freshness matters.
top
SaveBd
nSuccess := oCache:SaveBd(cKey, cExpiration, cEtag, oBd) // returns Numeric (1/0)
Introduced in version 11.0.0

Stores the contents of bd as binary cache data under key. If the key already exists, its data and metadata are replaced.

ArgumentPurpose
keyThe unique application-defined cache key.
expirationExpiration as an RFC 822-style Internet date string. Pass an empty string for no expiration.
etagOptional ETag or application metadata. Pass an empty string when unused.
bdThe BinData containing the bytes to save.
Expiration is not automatic deletion: An expired item remains present until it is replaced or explicitly removed. This permits stale-while-revalidate workflows but requires the application to check freshness.

Returns 1 for success, 0 for failure.

top
SaveTextDt
nSuccess := oCache:SaveTextDt(cKey, oExpireDateTime, cETag, cItemTextData) // returns Numeric (1/0)

Stores itemTextData as a text cache item under key, with the expiration date and time supplied in expireDateTime. If the key already exists, its data and metadata are replaced.

eTag is optional ETag or application metadata and may be an empty string. The key may contain any characters and may be any length, but it must uniquely identify the item.

Expiration does not delete: After the expiration time passes, the entry remains on disk and can still be fetched. Use LastHitExpired to detect staleness and a deletion method to remove it.

Returns 1 for success, 0 for failure.

top
SaveTextNoExpire
nSuccess := oCache:SaveTextNoExpire(cKey, cETag, cItemTextData) // returns Numeric (1/0)

Stores itemTextData as a non-expiring text cache item under key. If the key already exists, its data and metadata are replaced.

eTag is optional ETag or application metadata and may be an empty string.

Returns 1 for success, 0 for failure.

top
SaveTextStr
nSuccess := oCache:SaveTextStr(cKey, cExpireDateTime, cETag, cItemTextData) // returns Numeric (1/0)

Stores itemTextData as a text cache item under key, with expireDateTime providing the expiration time as an RFC 822-style Internet date string. If the key already exists, its data and metadata are replaced.

eTag is optional ETag or application metadata and may be empty.

Date alternatives: Use SaveTextDt when the expiration is available as a CkDateTime, or SaveTextNoExpire for an entry without expiration.

Returns 1 for success, 0 for failure.

top
UpdateExpirationDt
nSuccess := oCache:UpdateExpirationDt(cKey, oExpireDateTime) // returns Numeric (1/0)

Replaces the expiration date and time of the cache item identified by key with the CkDateTime value supplied in expireDateTime. The cached data and ETag are unchanged.

Existing item required: This method updates metadata; it does not create a new cache entry when the key is absent.

Returns 1 for success, 0 for failure.

top
UpdateExpirationStr
nSuccess := oCache:UpdateExpirationStr(cKey, cExpireDateTime) // returns Numeric (1/0)

Replaces the expiration date and time of the cache item identified by key with the RFC 822-style Internet date string supplied in expireDateTime. The cached data and ETag are unchanged.

Argument name: Some language bindings name key url; it is the cache key and does not need to be a URL. Use UpdateExpirationDt for a CkDateTime value.

Returns 1 for success, 0 for failure.

top

Deprecated

GetExpirationDt
oCkDateTime := oCache:GetExpirationDt(cKey) // returns CkDateTime
This method is deprecated.

Deprecated: Use GetExpirationStr and load the returned value into a CkDateTime when an object representation is required.

Returns the expiration date and time for the item identified by key as a newly returned CkDateTime object.

Returns NIL on failure

More Information and Examples
top