Download the PHP package egensolve/realtime without Composer

On this page you can find all versions of the php package egensolve/realtime. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Example code of egensolve/realtime

Informations about the package realtime

ERS PHP client

This framework-neutral package provides version 1 envelope validation, typed channel builders and parsing, backend channel-authorization signing, and a durable-publication client.

The publication client accepts an application-provided HTTP transport. That keeps the package free of framework and Composer runtime dependencies while allowing each application to use its existing HTTP stack. Remote publication endpoints must use HTTPS; plaintext HTTP is accepted only for loopback development hosts.

Application backends remain responsible for authenticating their users and deciding which channels they may access. Never place application secrets in browser or mobile clients.

Calls control channels

Use the provider-neutral CallChannel for a product-authorized Calls session's control feed:

Tenant identifiers allow 1–64 ASCII letters, digits, _ and -; call identifiers allow 1–128 of the same characters. Case is preserved. The complete channel must still fit 164 characters. Only the Calls shape uses private-v2; existing v1 channels are unchanged. The envelope remains version 1. Existing Auth\ChannelAuthSigner signs this private channel without presence data, after the backend has authorized access. Parsing a channel is not an authorization decision. This API carries control events, not audio/video, and does not supply a media client.

Media and Artifacts (trusted backends only)

Use Media\MediaClient for upload intents, interrupted-upload capability renewal, multipart part intents, completion, asset metadata, download grants and deletion. Use Artifacts\ArtifactsClient for artifact creation, revision upload/completion, publishing a revision and withdrawal. Both accept an ERS base URL, a server-held machine credential and an optional Http\Transport. The default Http\CurlTransport requires PHP's curl extension; injecting a transport keeps the protocol client dependency-free.

These clients send version-1 JSON metadata, not file bytes. Authorize the product user on your backend, request a short-lived upload/download instruction, then transfer bytes directly to its provider URL. Never embed machine credentials in a browser, mobile app or widget, and never log signed URLs or upload tokens. Preserve returned IDs exactly, including letter case.

Pass a stable idempotency key for retries of the same mutation; use a different key for a new operation. Inspect Http\ApiResponse::data for provider instructions and readiness. A successful completion request does not by itself mean an object is ready. Handle Http\ApiException status and error code; retry transient failures with backoff. Artifacts publishing accepts only a ready revision; republish an earlier ready revision to roll back, or withdraw to stop public delivery.

renewUploadCapability() reissues an expired provider PUT instruction for the same active upload. Pass upload_id and upload_token; include a positive part_number only for multipart renewal. Version 1 keeps both opaque upload values stable. Older provider capabilities remain valid only until their own expiry, and no renewed capability extends the asset retention deadline.

License

MIT. See LICENSE.

Media retention and tiering

Trusted product backends can use MediaClient.policy() to discover effective retention limits and permitted tiering profile IDs. updateRetention accepts an explicit ISO-8601 expiry or authorized null expiry and an idempotency key. Upload intents may select a permitted tiering_profile. These endpoints require a server supporting configurable retention and the appropriate machine-credential abilities; null expiry does not extend upload or download capabilities.

All versions of realtime with dependencies

PHP Build Version
Package Version
Requires php Version ^8.4
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package egensolve/realtime contains the following files

Loading the files please wait ...