Earlier versions of chunks use @do recall and @do remember, but these terms have multiple meanings in English. To avoid the potential for misunderstanding, and to benefit from a familiarity with HTTP, the names have been switched:
@do update to synchronously update the module buffer (this is the default action)
@do clear to synchronously clear the module buffer
@do get to request a matching chunk which is loaded into the module buffer
@do put to create a new chunk or overwrite one with the same ID
@do patch similar to put but only updates the properties passed in the action
@do delete delete matching chunks
In addition, you can use @status in a condition to check the status of the response to a previous request. It is set to pending, okay, forbidden, nomatch and failed as appropriate. To relate particular pairs of requests and responses, you can pass an identifier in an action with @tag and test for it with @tag in a subsequent rule condition.
Earlier versions of chunks use
@do recalland@do remember, but these terms have multiple meanings in English. To avoid the potential for misunderstanding, and to benefit from a familiarity with HTTP, the names have been switched:@do updateto synchronously update the module buffer (this is the default action)@do clearto synchronously clear the module buffer@do getto request a matching chunk which is loaded into the module buffer@do putto create a new chunk or overwrite one with the same ID@do patchsimilar toputbut only updates the properties passed in the action@do deletedelete matching chunksIn addition, you can use
@statusin a condition to check the status of the response to a previous request. It is set to pending, okay, forbidden, nomatch and failed as appropriate. To relate particular pairs of requests and responses, you can pass an identifier in an action with@tagand test for it with@tagin a subsequent rule condition.