Reactive framework inside the VM

# AxonLive brings real-time UX to Classic ASP applications.

AxonLive is integrated directly into AxonASP. User interactions are sent asynchronously, server logic executes securely, and only updated components are patched in the browser.

No full page reload Server-controlled state Session-bound security Builder support
Read AxonLive manual Open builder source

## Security model

- Async events are validated against ASPSESSIONID.
- Cross-session event injection is rejected by routing checks.
- Business logic remains on the backend instead of the browser.

## How AxonLive works

### 1. Page bootstrap

Server creates G3AXONLIVE object and calls InitPage to detect standard load versus async event request.

### 2. Client event capture

g3axonlive.js captures data-g3al attributes and sends event payloads to the runtime endpoint.

### 3. Server event routing

AxonLive reads EventComponentID and applies business logic using session-bound state values.

### 4. Targeted patch response

RegisterComponent queues updated fragments and EndAsyncResponse returns JSON patches only.

### 5. DOM update

The client bridge replaces affected components in place without reloading the entire page.

## Implementation reference

### Server-side lifecycle

    Set AxonLive = Server.CreateObject("G3AXONLIVE")
    AxonLive.InitPage()

    If AxonLive.IsAsyncRequest Then
        AxonLive.SetComponentProperty Session.SessionID, "main", "count", "42"
        AxonLive.RegisterComponent "counterDisplay", "<div id='counterDisplay'>42</div>"
        AxonLive.EndAsyncResponse()
    End If

### Client-side bootstrap

    <script src="/axonlive/g3axonlive.js"></script>
    <script>
        G3AxonLive.init();
    </script>

## AxonLive Builder and WASM mode

### Visual Builder

The builder in www/axonlive/builder offers drag-and-drop page composition and generates server-side JavaScript scaffolding for events and component routing.

### WASM compatibility

AxonLive in WASM maps component operations directly to browser DOM APIs, providing near-instant updates with API compatibility to the server-side model.

Architectural advantage: your team keeps a single reactive model across server mode and WASM mode with shared component semantics.