xp-forge/rest-client
Composer 安装命令:
composer require xp-forge/rest-client
包简介
REST Client
README 文档
README
REST client
Usage
The Endpoint class serves as the entry point to this API. Create a new instance of it with the REST service's endpoint URL and then invoke its resource() method to work with the resources.
Creating: post
use webservices\rest\Endpoint; $api= new Endpoint('https://api.example.com/'); $result= $api->resource('users')->post(['name' => 'Test'], 'application/json'); // Get location from created response, raising an UnexpectedStatus // exception for any statuscode outside of the range 200-299. $url= $result->location(); // Same as above, but handle 201 *AND* 200 status codes - see // https://stackoverflow.com/questions/1860645 $id= $result->match([ 200 => fn($r) => $r->value()['id'], 201 => fn($r) => (int)basename($r->location()) ]);
Reading: get / head
use webservices\rest\Endpoint; $api= new Endpoint('https://api.example.com/'); // Test for existance with HEAD, raising UnexpectedStatus exceptions // for any status code other than 200 and 404. $exists= $api->resource('users/1549')->head()->match([ 200 => true, 404 => false ]); // Return user object, raising an UnexpectedStatus exception for any // statuscode outside of the range 200-299. $user= $api->resource('users/self')->get()->value(); // Same as above, but returns NULL for 404s instead of an exception $user= $api->resource('users/{0}', [$id])->get()->optional(); // Pass parameters $list= $api->resource('user')->get(['page' => 1, 'per_page' => 50])->value(); // Access pagination via `Link: <...>; rel="next"` header $resource= 'groups'; do { $result= $this->endpoint->resource($resource)->get(['per_page' => 200]); foreach ($result->value() as $group) { yield $group['id'] => $group; } } while ($resource= $result->link('next'));
Updating: put / patch
use webservices\rest\Endpoint; $api= new Endpoint('https://api.example.com/'); $resource= $api->resource('users/self') ->sending('application/json') ->accepting('application/json') ; // Default content type and accept types set on resource used $updated= $resource->put(['name' => 'Tested', 'login' => $mail])->value(); // Resources can be reused! $updated= $resource->patch(['name' => 'Changed'])->value();
Deleting: delete
use webservices\rest\Endpoint; $api= new Endpoint('https://api.example.com/'); // Pass segments, map 204 to true, 404 to null, raise UnexpectedStatus // exception otherwise $api->resource('users/{id}', $user)->delete()->match([ 204 => true, 404 => null ]);
Uploads
Multipart file uploads are initiated by the upload() method, may include parameters and can upload from any input stream.
use io\File; use io\streams\MemoryInputStream; use webservices\rest\Endpoint; $stream= new MemoryInputStream('Hello'); $file= new File(...); $endpoint= new Endpoint($url); $result= $endpoint->resource('files')->upload() ->pass('tc', 'accepted') ->transfer('letter', $stream, 'letter.txt', 'text/plain') ->transfer('cv', $file->in(), $file->filename) ->finish() ;
Deserialization
Automatic result deserialization is supported by passing a type to the value() method.
use com\example\api\types\User; $result= $api->resource('users/{0}', [$id])->get(); // If a type is passed, the result will be unmarshalled to an object $map= $result->value(); $object= $result->value(User::class); // Same for optional, but map and object will be NULL for 404s $map= $result->optional(); $object= $result->optional(User::class); // Works with any type from the XP typesystem, e.g. arrays of objects $list= $api->resource('users')->get()->value('org.example.User[]');
Error handling
Operations on the Result class raise UnexpectedStatus exceptions. Here's how to access their status and reason:
use webservices\rest\UnexpectedStatus; use util\cmd\Console; // In unexpected cases try { $user= $api->resource('users/self')->get()->value(); } catch (UnexpectedStatus $e) { Console::writeLine('Unexpected ', $e->status(), ': ', $e->reason()); } // More graceful handling $result= $api->resource('users/self')->get(); if ($error= $result->error()) { Console::writeLine('Unexpected ', $result->status(), ': ', $error); } else { $user= $result->value(); }
Authentication
Basic authentication is supported by embedding the credentials in the endpoint URL:
use webservices\rest\Endpoint; $api= new Endpoint('https://user:pass@api.example.com/');
Bearer tokens can also be embedded in the endpoint URL:
use webservices\rest\Endpoint; $api= new Endpoint('https://token@api.example.com/');
Other header-based authentication values can be passed along as follows:
use webservices\rest\Endpoint; $api= (new Endpoint('https://api.example.com/'))->with(['X-API-Key' => $key]);
Compression
This library handlees compressed data transparently, sending an Accept-Encoding header containing compression algorithms supported in the PHP setup (based on loaded extensions like e.g. zlib) and using the Content-Encoding response header to determine which algorithm to select.
use webservices\rest\Endpoint; use io\streams\Compression; // Detect supported compression algorithms and set "Accept-Encoding" accordingly $endpoint= new Endpoint($api); // Send "Accept-Encoding: identity", indicating the server should not compress $endpoint= (new Endpoint($api))->compressing(Compression::$NONE); // Send "Accept-Encoding: gzip, br" $endpoint= (new Endpoint($api))->compressing(['gzip', 'br']); // Do not send an "Accept-Encoding" header, i.e. no preference is expressed $endpoint= (new Endpoint($api))->compressing(null);
Testability
This library also includes facilities to ease writing unittests for code making REST API calls. By using the TestEndpoint class and supplying it with routes it should respond to, various scenarios can be easily tested without the need for HTTP protocol and I/O overhead.
use webservices\rest\TestEndpoint; $endpoint= new TestEndpoint([ '/users/6100' => function($call) { return $call->respond(200, 'OK', ['Content-Type' => 'application/json'], '{ "id": 6100, "username": "binford" }'); }, 'POST /users' => function($call) { return $call->respond(201, 'Created', ['Location' => '/users/6100']); }, ]); $response= $endpoint->resource('/users/me')->get(); // Responds with HTTP status 200 and the above JSON payload
xp-forge/rest-client 适用场景与选型建议
xp-forge/rest-client 是一款 基于 PHP 开发的 Composer 扩展包,目前已累计 49.98k 次下载、GitHub Stars 达 0, 最近一次更新时间为 2018 年 08 月 30 日, 在 PHP 生态内属于活跃度较高的组件。
它主要适用于以下技术方向: 「module」 「xp」 等业务场景。在实际项目中,围绕这些方向常见需要落地的问题包括:接口对接、性能调优、并发安全、与既有框架(Laravel / ThinkPHP / Yii / Webman 等)的兼容适配,以及生产环境的日志埋点与稳定性保障。
我们在过去多个企业项目中使用过 xp-forge/rest-client 或与其功能相近的方案,如果你在选型或落地过程中遇到问题,例如 版本兼容、二次改造、私有化封装、与内部系统对接、生产 BUG 排查,欢迎联系我们协助评估。
基于 xp-forge/rest-client 在你已有业务上做功能扩展、字段裁剪、UI 适配、与内部账号 / 权限 / 日志系统的深度对接。
线上偶发问题、内存泄漏、慢查询、并发异常等排查修复;针对高流量场景做缓存、队列、索引层面的调优。
承接完整的项目从需求 → 设计 → 开发 → 上线 → 长期运维;也可按月提供技术保姆服务。
与 xp-forge/rest-client 相关的其它包
同方向 / 同关键字的高下载量 PHP Composer 包推荐,方便对比选型:
bootstrap select field module implementing http://silviomoreto.github.io/bootstrap-select/
Yii2 module to manage website content. Kind of a CMS...
Codeurx Modular is simply a package for Laravel to help you create and manage modules.
User Module for the Attogram Framework
Info Module for the Attogram Framework
Contact Form Module for the Attogram Framework
统计信息
- 总下载量: 49.98k
- 月度下载量: 0
- 日度下载量: 0
- 收藏数: 0
- 点击次数: 10
- 依赖项目数: 3
- 推荐数: 0
其他信息
- 授权协议: BSD-3-Clause
- 更新时间: 2018-08-30

