Libraries tagged by mesh
visavi/watermask
6 Downloads
Overlay mesh watermark image
reida010/drupal
1 Downloads
Mesh.lu project template for Drupal 9 projects with Composer
oneiota/config
5 Downloads
Client library for MESH Config.
nodeum-io/nodeum-sdk-php
0 Downloads
The Nodeum API makes it easy to tap into the digital data mesh that runs across your organisation. Make requests to our API endpoints and we’ll give you everything you need to interconnect your business workflows with your storage. All production API requests are made to: http://nodeumhostname/api/ The current production version of the API is v1. **REST** The Nodeum API is a RESTful API. This means that the API is designed to allow you to get, create, update, & delete objects with the HTTP verbs GET, POST, PUT, PATCH, & DELETE. **JSON** The Nodeum API speaks exclusively in JSON. This means that you should always set the Content-Type header to application/json to ensure that your requests are properly accepted and processed by the API. **Authentication** All API calls require user-password authentication. **Cross-Origin Resource Sharing** The Nodeum API supports CORS for communicating from Javascript for these endpoints. You will need to specify an Origin URI when creating your application to allow for CORS to be whitelisted for your domain. **Pagination** Some endpoints such as File Listing return a potentially lengthy array of objects. In order to keep the response sizes manageable the API will take advantage of pagination. Pagination is a mechanism for returning a subset of the results for a request and allowing for subsequent requests to “page” through the rest of the results until the end is reached. Paginated endpoints follow a standard interface that accepts two query parameters, limit and offset, and return a payload that follows a standard form. These parameters names and their behavior are borrowed from SQL LIMIT and OFFSET keywords. **Versioning** The Nodeum API is constantly being worked on to add features, make improvements, and fix bugs. This means that you should expect changes to be introduced and documented. However, there are some changes or additions that are considered backwards-compatible and your applications should be flexible enough to handle them. These include: - Adding new endpoints to the API - Adding new attributes to the response of an existing endpoint - Changing the order of attributes of responses (JSON by definition is an object of unordered key/value pairs) **Filter parameters** When browsing a list of items, multiple filter parameters may be applied. Some operators can be added to the value as a prefix: - `=` value is equal. Default operator, may be omitted - `!=` value is different - `>` greater than - `>=` greater than or equal - `=` lower than or equal - `>
alibabacloud/servicemesh-20200111
6 Downloads
Alibaba Cloud Alibaba Cloud Service Mesh (20200111) SDK Library for PHP
psr/http-message
776757329 Downloads
Common interface for HTTP messages
guzzlehttp/psr7
768767384 Downloads
PSR-7 message implementation that also provides common utility methods
webmozart/assert
699499835 Downloads
Assertions to validate method input/output with nice error messages.
symfony/var-dumper
637107371 Downloads
Provides mechanisms for walking through any arbitrary PHP variable
symfony/mime
470181277 Downloads
Allows manipulating MIME messages
sebastian/code-unit-reverse-lookup
604747106 Downloads
Looks up which function or method a line of code belongs to
symfony/psr-http-message-bridge
203447199 Downloads
PSR HTTP message bridge
php-http/message
200503095 Downloads
HTTP Message related tools
php-http/message-factory
229263648 Downloads
Factory interfaces for PSR-7 HTTP Message
psr/http-factory
459977864 Downloads
PSR-17: Common interfaces for PSR-7 HTTP message factories