One post tagged with "websockets"

BowPHP is a request/response framework — it shines at HTTP: routing, validation, the Barry ORM, sessions. What it deliberately does not ship is a long-running WebSocket server, because keeping a socket open for every visitor is a different job from answering an HTTP request and moving on.

So the right architecture isn't "make BowPHP do WebSockets." It's: let BowPHP do what it's great at — validate and persist messages, and be the source of truth — and put a tiny, dumb socket.io server next to it whose only job is to fan messages out to connected browsers in real time.

That's exactly what we'll build: a small group chat where BowPHP owns the data and a ~30-line Node server owns the live connection.