How sibidharan/zealphp works
ZealPHP is a long-running PHP HTTP server built on OpenSwoole. The principal workflow accepts an HTTP request, dispatches it through middleware and route or file-based API handling, then emits an HTTP response. Its other major product branches include coroutine-safe legacy PHP compatibility and sessions, WebSockets and streaming, shared storage and cross-node messaging, timers, and templating. The README documents these capabilities; unsampled implementation details are represented only where paths are supported, and uncertain connections are omitted.
Main entry points: App.php App server · ResponseMiddleware.php Middleware stack · Store.php Shared Store · ApiDispatchHandler.php API dispatch
Components 22
Server runtime
- App server
src/App.php - Request context
src/RequestContext.php - Coroutine runtime
src/App.php - Timers
src/App.php
HTTP handling
- Middleware stack
src/ResponseMiddleware.php - Route dispatch
src/Middleware/Pipeline/RouteDispatchHandler.php - Path dispatch
src/Middleware/Pipeline/PathDispatchHandler.php - API dispatch
src/Middleware/Pipeline/ApiDispatchHandler.php - ZealAPI endpoints
src/ZealAPI.php - HTTP request
src/HTTP/Request.php - HTTP response
src/HTTP/Response.php
State and realtime
- Shared Store
src/Store.php - Redis backend
src/Store/RedisBackend.php - Redis client
src/Store/RedisClient.php - Shared Counter
src/Counter.php - WebSocket router
src/WSRouter.php
Compatibility and output
- Session manager
src/Session/SessionManager.php - Legacy compatibility
src/Session/SessionManager.php - Legacy CGI workers
src/CGI/WorkerPool.php - Templating
src/App.php - SSE streaming
src/HTTP/Response.php
Other components
- HTTP client
Connections 23
- HTTP client → App server: sends request
README.md - App server → Middleware stack: configures middleware
src/ResponseMiddleware.php - Middleware stack → Route dispatch: dispatches routes
src/ResponseMiddleware.php - Middleware stack → Path dispatch: dispatches paths
src/ResponseMiddleware.php - App server → API dispatch: registers API dispatch
src/Middleware/Pipeline/ApiDispatchHandler.php - API dispatch → ZealAPI endpoints: invokes endpoints
src/Middleware/Pipeline/ApiDispatchHandler.php - ZealAPI endpoints → HTTP request: uses request
src/ZealAPI.php - Middleware stack → HTTP response: builds response
src/ResponseMiddleware.php - HTTP request → Request context: request state
- App server → Coroutine runtime: runs coroutines
README.md - App server → Timers: schedules timers
README.md - App server → Session manager: supports sessions
README.md - Session manager → Request context: uses request state
src/Session/SessionManager.php - App server → Legacy compatibility: isolates legacy state
README.md - App server → Legacy CGI workers: offers CGI mode
README.md - App server → Templating: renders templates
README.md - HTTP response → SSE streaming: streams events
README.md - App server → WebSocket router: registers WebSockets
README.md - WebSocket router → Shared Store: routes shared messages
src/WSRouter.php - App server → Shared Store: shares state
README.md - Shared Store → Redis backend: selects backend
src/Store.php - Redis backend → Redis client: uses client
src/Store/RedisBackend.php - App server → Shared Counter: provides counters
README.md