Web Services

API 設計方式主要有三種: REST, XML-RPC, SOAP 資料格式常見 JSON, XML。 The Web Services API for Plone (wsapi4plone) is a Zope 2 package that provides an XML-RPC Application Programming Interface (API) for the Plone.

Web API get post my-top-5-apis-for-new-developers CQRS 實現方法 API grpc protobuf wrong https://medium.com/@pragprog/why-use-protocol-buffers-fb43d4e912ef

export 試試看這個 es-modules-in-browsers API Intro From Monolith To Cloud Series HelloSign API API Future Microservice Architecture at Medium Microservice Architecture through Story

Web Service 透過 HTTP 協定和 API 來提供軟體功能，通常是給另一個程式使用，而非直接和使用者互動。利用 URL 來存取，回傳的資料常使用 XML 或 JSON 格式，再由程式解析利用。常見的 Web Service 有 REST 和 SOAP 兩大形式協定。

最基本的 Web Service 需要實作 GetCapabilities 和 GetMap，額外可以實作 GetFeatureInfo，WMS 並沒有規範 tile，而另有 WEM Tiling Client Recommendation 來確保產生的地圖包含固定大小的 tile。OpenLayers 是支援多重圖疊的 Javascript 函式庫，應用時要先建立 HTML 檔案，載入使用者的瀏覽器後，再撰寫 Javascript 存取 OpenLayers API 來建立需要的地圖。

Apache Kafka Inspiration for Events Architecture

API first Programming on the Front-end

API Design: Stop Thinking About URLs 診所提供病患與醫生的預約機制

GraphQL + Koa + MongoDB

Microservices

Invaluable Guide Building Microservices with Python

早期 latency 議題在 gRPC 問世後大幅改善透過 Protocol Buffer 定義 Model

Kong API Gateway

利用 WebSocket 在內容變動時自動更新頁面安全議題 REST vs WebSockets Domain Driven Design in the era of Microservices

REST API

何時要用 PATCH 其優缺點是? PUT 和 PATCH 都可以 Update 資料但 PATCH 只針對局部資料失敗的話不會自動重傳原本不存在的資源也不會被建立 safe 是指「該操作不會改變伺服器的資源狀態而且結果可以被快取」 idempotent 是指「該操作重覆執行都會得到同樣的資源狀態結果但不一定得到同樣的回傳值例如 DELETE 第二次可能回傳 404」

RESTful design 對應 CRUD 想像成街道上的建築物

plone.rest 提供 HTTP verb 功能，是協助建立 RESTful endpoint 的底層服務，因為是獨立的套件，也提供另建 endpoint 的彈性。實際操作則透過 plone.restapi 執行。

以 @search 為例，它的篩選格式跟 @@search 類似，但兩者實作仍有不同，像是沒有 * 模糊比對。

plone.rest fix allow_headers edi.restreader/retaccess.py

@users endpoint @theme endpoint barceloneta-mocks Redirect Handling Flask Example Clear a DateTime Field

How It Begins API Discussion RESTful API vs HTTP API: Microsoft Case GraphQL vs REST API URL Shortener with React Apollo GraphQL VCRPY: API Test Tool

JSON Content Type MIME: application/json JSONP: application/javascript Why Should Not Use text/html for JSON

JSON Server to build Fake REST API

Major Categories REST for Plone 2013-04-15

Build Fast REST APIs with Node.js MongoDB Fastify Swagger

WebLion subversion

REST API 並不是資料庫 plone.restapi 相依關係 plone.rest PyJWT collective.jsonify

範例: plone.jsonapi.routes 新增 author 資訊

DeprecationWarning: getSiteEncoding is deprecated. Plone only supports UTF-8 currently. This method always returns "utf-8"

Gull

OData

python-odata

GraphQL

Introduction to GraphQL Graphpack: Create with Zero Configuration GraphQL 比較 REST 優點簡介 MongoDB + Hapi + Swagger

使用經驗架構項目: Schema Definition Language (SDL), Type, Query, Mutation, Subscription

Search Indexing

WSGI

Hanno Schlichting: Zope2 4.0 the main goal was to make it possible to run Zope without all of these extra protocols, so applications like Plone can decide what they want to use. And hopefully porting to Python 3 becomes easier with fewer I/O boundaries to take care of.

Packages using the API

msp2plone -- A Microsoft Project XML to Plone 'eXtreme Management' importer.
collective.contentrules.wsapi4plone -- A collection of rules for sending content from one Plone site to another on content events, such as when a content object is modified.
Parfait-- AtomPub WSGI middleware to enable the Atom Publication Protocol in Plone.
wsapi4plone.client -- An XML-RPC client built specifically to interact with Plone.
wsapi4plone.webslinger -- An extendable client package for importing content into Plone.
wsapi4plone.remotemgmt -- A Plone product for managing Plone sites from a remote application.
PloneBatcher -- A package for batch processing Plone content creation, extraction, and updates.

Web Services

Microservices

REST API

OData

GraphQL

WSGI

Packages using the API

Overview of Enhancements and Bug Fixes

Specifications and Data Formats

Standard APIs

More Information

Related Information