JumPHP engine extension: big game data streamed from the playground (jumphp/externals)
- PHP 100%
| Filename | Latest commit message | Latest commit date |
|---|---|---|
On disk, outside the engine's memory (IndexedDB lives in memory in the browser): a game with big files can keep persist: false and still not download them twice. Co-Authored-By: Claude Opus 5.5 <[email protected]> |
||
| doc | ||
| src | ||
| AGENTS.md | ||
| composer.json | ||
| LICENSE | ||
| README.md | ||
jumphp/externals
A JumPHP engine extension: big game data streamed from the playground. The administrator
shares folders of the server's externals/ with chosen games; a game lists them, searches them and reads files like
a disk: only the 64 KB blocks it reads are downloaded (HTTP Range), cached in memory and in the player's storage.
On the desktop and in tests, local folders stand in for the server.
bin/jumphp composer mygame require jumphp/externals
$this->externals->open('mygame/data/level1.bin')->then(
fn (\JumPHP\Externals\RemoteFile $f) => $f->read(1024, 64)->then(fn (string $bytes) => ...));
Documentation: doc/index.md; tutorial: doc/tutorial.md; samples: doc/samples/; example game: games/externals-demo.
MIT licence.