Code as Server Model: This demo uses a standalone Mojolicious server running as a persistent process.
Sessions are stored in-memory on the server, providing fast access but lost on server restart.
Apache proxies requests to the Mojolicious server running on port 8080.
Set Your Name
Session Pages
- Session Page 1 - View/set session data
- Session Page 2 - Verify session persists
- Destroy Session - Clear session data
How It Works
- Enter your name and click "Set Name"
- Your name is stored in the server's memory (Mojolicious session)
- Navigate between pages - your name persists
- The session is tied to a signed cookie in your browser
- Click "Destroy Session" to clear the server-side data
Comparing Session Storage
| Approach | Storage Location | Persistence | Speed |
|---|---|---|---|
| Mojolicious (Code as Server) | Server memory (signed cookie) | Lost on restart | Fast |
| Perl CGI | File system (/tmp) | Survives restart | Slower (disk I/O) |