Scenario: server-side update (fragments)

The server decides which containers refresh. Each action calls AjaxUpdater.add/set/clear, and the chosen containers come back as <ajaxslim-fragment>s in this response — one round-trip, no AUC.update JavaScript. The link itself declares no updateContainerID.

Server decides the whole set

The link declares no updateContainerID — the server picks every container.

Augment · two add basicInfo + bottomContainer

Augment · one add basicInfo only

Replace set bottomContainer only

Clear clear — renders nothing, but the action ran: it resets the counters (visible on the next press)

Client requests, server amends

The link asks for basicInfo; the action adds bottomContainer on top — both refresh.

Amend client basicInfo + server add bottomContainer

Server-side update targeting

Server decides the whole set

Client requests, server amends

Containers