Tornado 4.5 Documentation
tornado.wsgi — Interoperability with other Python frameworks and servers tornado.platform.asyncio — Bridge between asyncio and Tornado tornado.platform.caresresolver — Asynchronous DNS Resolver using C-Ares methods to log users in via these sites and, where applicable, methods to authorize access to the service so you can, e.g., download a user’s address book or publish a Twitter message on their behalf. Here Running Tornado apps on WSGI servers Running WSGI apps on Tornado servers tornado.platform.asyncio — Bridge between asyncio and Tornado tornado.platform.caresresolver — Asynchronous DNS Resolver using C- Ares0 码力 | 333 页 | 322.34 KB | 1 年前3Guzzle PHP 5.3 Documentation
verify the Content-MD5 headers of responses. Service Description Commands You can use the Guzzle Command library to encapsulate interaction with a web service using command objects. Building on top of Guzzle’s allows you to easily implement things like service description that can be used to serialize requests and parse responses using a meta-description of a web service. Guzzle Command [https://github.com/guzzle/command] command based, web service clients with Guzzle. Guzzle Services [https://github.com/guzzle/guzzle-services] Provides an implementation of the Guzzle Command library that uses Guzzle service descriptions to0 码力 | 72 页 | 312.62 KB | 10 月前3Cilium v1.6 Documentation
configuration. Why Cilium? The development of modern datacenter applications has shifted to a service-oriented architecture often referred to as microservices, wherein a large application is split into to transparently insert security visibility + enforcement, but does so in a way that is based on service / pod / container identity (in contrast to IP address identification in traditional systems) and requests with method GET and path /public/.*. Deny all other requests. Allow service1 to produce on Kafka topic topic1 and service2 to consume on topic1. Reject all other Kafka messages. Require the HTTP header0 码力 | 734 页 | 11.45 MB | 1 年前3BAETYL 0.1.6 Documentation
Welcome to BAETYL’s documentation! [https://baetyl.io/en/] Baetyl, extend cloud computing, data and service seamlessly to edge devices. BAETYL Home [https://baetyl.io/en/] Overview What is Baetyl Advantages Baetyl with Hub service Workflow Connection Test Message transferring among devices with Local Hub Service Workflow Message Routing Test Message handling with Local Function Service Workflow Message framework of Linux Foundation Edge [https://www.lfedge.org] that extends cloud computing, data and service seamlessly to edge devices. It can provide temporary offline, low-latency computing services, and0 码力 | 119 页 | 11.46 MB | 1 年前3Tornado 5.1 Documentation
C-Ares tornado.platform.twisted — Bridges between Twisted and Tornado tornado.platform.asyncio — Bridge between asyncio and Tornado Utilities tornado.autoreload — Automatically detect code changes in methods to log users in via these sites and, where applicable, methods to authorize access to the service so you can, e.g., download a user’s address book or publish a Twitter message on their behalf. Here and Tornado Twisted on Tornado Tornado on Twisted Twisted DNS resolver tornado.platform.asyncio — Bridge between asyncio and Tornado tornado.auth — Third-party login with OpenID and OAuth This module0 码力 | 359 页 | 347.32 KB | 1 年前3Pro Git 2nd Edition 2.1.413
deftly juggle numerous remote branches and contributed patches. Chapter 6 covers the GitHub hosting service and tooling in depth. We cover signing up for and managing an account, creating and using Git repositories if you have access, push over. Dumb HTTP If the server does not respond with a Git HTTP smart service, the Git client will try to fall back to the simpler Dumb HTTP protocol. The Dumb protocol expects special daemon that comes packaged with Git; it listens on a dedicated port (9418) that provides a service similar to the SSH protocol, but with absolutely no authentication or cryptography. In order for0 码力 | 731 页 | 21.49 MB | 1 年前3Pro Git 2nd Edition 2.1.413
deftly juggle numerous remote branches and contributed patches. Chapter 6 covers the GitHub hosting service and tooling in depth. We cover signing up for and managing an account, creating and using Git repositories if you have access, push over. Dumb HTTP If the server does not respond with a Git HTTP smart service, the Git client will try to fall back to the simpler Dumb HTTP protocol. The Dumb protocol expects special daemon that comes packaged with Git; it listens on a dedicated port (9418) that provides a service similar to the SSH protocol, but with absolutely no ▪ ▪ authentication or cryptography. In order0 码力 | 691 页 | 13.35 MB | 1 年前3BAETYL 1.0.0 Documentation
Welcome to BAETYL’s documentation! [https://baetyl.io/en/] Baetyl, extend cloud computing, data and service seamlessly to edge devices. BAETYL Home [https://baetyl.io/en/] Overview What is Baetyl Baetyl connect to Hub Service Message transferring among devices with Hub Service Message handling with Function Service Message Synchronize between baetyl-hub and Baidu IoTHub via Remote Service Image capturing capturing and AI model inference with Video infer Service Development How to write a python script for Python runtime How to write a javascript for Node runtime How to import third-party libraries for Python0 码力 | 135 页 | 15.44 MB | 1 年前3Tornado 6.2 Documentation
C-Ares tornado.platform.twisted — Bridges between Twisted and Tornado tornado.platform.asyncio — Bridge between asyncio and Tornado Utilities tornado.autoreload — Automatically detect code changes in methods to log users in via these sites and, where applicable, methods to authorize access to the service so you can, e.g., download a user’s address book or publish a Twitter message on their behalf. Here argument is passed to listen() you can run the program multiple times to create a multi-process service. 2. add_sockets: multi-process: sockets = bind_sockets(8888) tornado.process.fork_processes(0)0 码力 | 407 页 | 385.03 KB | 1 年前3Cilium v1.7 Documentation
configuration. Why Cilium? The development of modern datacenter applications has shifted to a service-oriented architecture often referred to as microservices, wherein a large application is split into to transparently insert security visibility + enforcement, but does so in a way that is based on service / pod / container identity (in contrast to IP address identification in traditional systems) and requests with method GET and path /public/.*. Deny all other requests. Allow service1 to produce on Kafka topic topic1 and service2 to consume on topic1. Reject all other Kafka messages. Require the HTTP header0 码力 | 885 页 | 12.41 MB | 1 年前3
共 578 条
- 1
- 2
- 3
- 4
- 5
- 6
- 58