Libraries tagged by client-side
zachleigh/laravel-laundromat
18 Downloads
Clean up objects before sending them client-side.
wanmendoza/prerender-bundle
8 Downloads
Allows you to easily use prerender for your Symfony apps running Client-Side MVC
vvg/filterlist-bundle
85 Downloads
Bundle to generate dynamic filtered (client-side) lists using jQuery.
venne/holder-module
696 Downloads
Holder renders image placeholders entirely on the client side.
user1007017/yii2-hyphenator
30 Downloads
Yii2 extension that provides client-side hyphenation of HTML documents
uniter/cube-demo
13 Downloads
Demo hybrid Three.js JS/PHP client-side app with Uniter-Loader
undf/angular-utrans
101 Downloads
Symfony2 and AngularJS module for client side translations
tslol/docker-api-php
2 Downloads
The Engine API is an HTTP API served by Docker Engine. It is the API the Docker client uses to communicate with the Engine, so everything the Docker client can do can be done with the API. Most of the client's commands map directly to API endpoints (e.g. `docker ps` is `GET /containers/json`). The notable exception is running containers, which consists of several API calls. # Errors The API uses standard HTTP status codes to indicate the success or failure of the API call. The body of the response will be JSON in the following format: ``` { "message": "page not found" } ``` # Versioning The API is usually changed in each release, so API calls are versioned to ensure that clients don't break. To lock to a specific version of the API, you prefix the URL with its version, for example, call `/v1.30/info` to use the v1.30 version of the `/info` endpoint. If the API version specified in the URL is not supported by the daemon, a HTTP `400 Bad Request` error message is returned. If you omit the version-prefix, the current version of the API (v1.44) is used. For example, calling `/info` is the same as calling `/v1.44/info`. Using the API without a version-prefix is deprecated and will be removed in a future release. Engine releases in the near future should support this version of the API, so your client will continue to work even if it is talking to a newer Engine. The API uses an open schema model, which means server may add extra properties to responses. Likewise, the server will ignore any extra query parameters and request body properties. When you write clients, you need to ignore additional properties in responses to ensure they do not break when talking to newer daemons. # Authentication Authentication for registries is handled client side. The client has to send authentication details to various endpoints that need to communicate with registries, such as `POST /images/(name)/push`. These are sent as `X-Registry-Auth` header as a [base64url encoded](https://tools.ietf.org/html/rfc4648#section-5) (JSON) string with the following structure: ``` { "username": "string", "password": "string", "email": "string", "serveraddress": "string" } ``` The `serveraddress` is a domain/IP without a protocol. Throughout this structure, double quotes are required. If you have already got an identity token from the [`/auth` endpoint](#operation/SystemAuth), you can just pass this instead of credentials: ``` { "identitytoken": "9cbaf023786cd7..." } ```
trackfinity/trackfinity-php-client
6 Downloads
Client side library for rule based traffic filtering on a web site.
tohir/formgenerator
167 Downloads
PHP Form Generator with both Client-Side (jQuery Validation Plugin) and Server-Side Validation
swayok/page.js
61 Downloads
Tiny client-side router
stegback/ratepay
19 Downloads
ratepay package is for communication beetween client side and ratepay api, you can send direct array to xml api request.
spirit-dev/oauth2-client-bundle
31 Downloads
Symfony OAuth2 Bundle client side
smoq/database-dump-bundle
2 Downloads
A small Symfony bundle that allows for database dump from the client side in excel or sql format
sleepness/uber-frontend-validation-bundle
14 Downloads
Provides a powerful tool for client side validation form data