Engi
Native networking stack for Amiga
Engi (縁起) — the fundamental interconnectedness of all things: nothing exists in isolation; every part arises in relation to the whole. The Engi stack brings that idea to Amiga networking: service discovery, HTTP, and TLS as shared infrastructure that applications can compose rather than reimplement.
Engi is the amigazen project’s answer to the missing modern network layer on classic Amiga. Where FastForward provides pluggable multimedia plumbing, Engi provides pluggable network plumbing — a coherent stack for finding services on the LAN, speaking HTTP, and securing connections with TLS.
Components
| Component |
Role |
Status |
| AmiATP |
AT Protocol client API for Amiga (amiatp.library): session, repo, and Bluesky-compatible protocol calls for apps built on Engi. |
Work in progress — GitHub |
| AmiFTP |
FTP client for Amiga: browse, transfer, and manage remote files over the classic File Transfer Protocol. |
Alpha — GitHub |
| AmiHTTP |
HTTP client and server stack for Amiga: request/response handling, streaming bodies, and the foundation for web-aware applications, browsers, and media sources. |
Work in progress — GitHub |
| AmiTLS |
TLS stack for Amiga: secure sockets for HTTPS and other encrypted protocols, designed to integrate with AmiHTTP and third-party clients. |
Work in progress — GitHub |
| Bonami |
mDNS and DNS-SD stack for zero-configuration service discovery and registration on the local network. |
Work in progress — GitHub |
| HTTPMount |
HTTP/HTTPS DOS handler for mounting remote web resources as Amiga volumes, built on AmiHTTP. |
Work in progress — GitHub |
| Seiten |
Bluesky app for Amiga, built on AmiATP and the Engi HTTP/TLS stack. |
Work in progress — GitHub |
Relationship to ToolKit
AmiATP, AmiFTP, AmiHTTP, AmiTLS, Bonami, HTTPMount, and Seiten live under Engi as first-class networking and online-service projects. ToolKit remains the universal SDK and build standard; Engi is where network stack development lives, with the same open-source ethos and ToolKit-compatible builds.
Who it is for
• Application authors who need HTTP or HTTPS without bundling a one-off client
• Browser and media projects (AWeb, FastForward, Voyager) that need a shared HTTP/TLS layer
• Server and utility authors who want Bonjour-compatible service advertisement on Amiga LANs
• Anyone building connected Amiga software on classic hardware
Documentation for individual components will appear here as each reaches public alpha. Pull requests and issue reports are welcome on GitHub.
|
|