HTTP
Core Facts
RESTful API uses URLs to represent resources, HTTP methods to represent operations (GET for query, POST for creation, PUT for update, DELETE for deletion), and HTTP status codes to represent results.
WebSocket is a protocol for full-duplex communication over a single TCP connection, allowing the server to proactively push data to the client.
Idempotency refers to the property whereby executing the same operation once produces exactly the same effect as executing it multiple times, with HTTP PUT/DELETE methods and database INSERT OR IGNORE semantics being typical examples
Timeline (last 90 days)
AI agents join the game via ordinary HTTP, read a skill file, pick a name, and can start playing, with no dedicated SDK required.
The HTTP protocol defines how browsers and servers talk to each other.
The engineering implementation of a 'two-way channel' usually takes two forms: in-process integration (LLM call logic written into game scripts, reading and writing world state through the engine's scripting API) and out-of-process communication (the game side opens a local service or message channel such as HTTP or WebSocket, and the agent runs as a separate process requesting state and issuing commands).
Agent development is not an entirely new body of knowledge; under the hood, most agent frameworks are still HTTP requests, JSON serialization and asynchronous task scheduling.
The 404 page is a standard status code in the HTTP protocol, indicating that the server cannot find the resource requested by the user.
HTTP compression works by the client sending an Accept-Encoding request header to declare supported compression algorithms, and if the server agrees, it returns Content-Encoding in the response header and sends compressed data.
The identity attribution of an AI agent (which user, which platform it represents) is often invisible at the HTTP layer, making it hard for websites to judge its commercial nature from request characteristics alone.
The OTLP protocol choice affects only the transport layer, not data semantics, so switching between gRPC and HTTP carriage does not change metric names or labels.
The HTTP protocol is easier to debug and easier for various language stacks to integrate than proprietary RPC, at the cost of possibly being inferior to shared-memory or RDMA solutions in ultra-low-latency scenarios; the specific trade-off depends on whether the protocol implementation supports batch and streaming transfer.
The traditional HTTP request-response model assumes the caller waits in place for the result to return, but the time scale of human decisions (minutes to hours) far exceeds the lifetime of an HTTP connection.
40 more timeline events
All Facts (20)
RESTful API uses URLs to represent resources, HTTP methods to represent operations (GET for query, POST for creation, PUT for update, DELETE for deletion), and HTTP status codes to represent results.
90%VerifiedWebSocket is a protocol for full-duplex communication over a single TCP connection, allowing the server to proactively push data to the client.
90%VerifiedIdempotency refers to the property whereby executing the same operation once produces exactly the same effect as executing it multiple times, with HTTP PUT/DELETE methods and database INSERT OR IGNORE semantics being typical examples
70%VerifiedThe IETF is the primary international body responsible for developing Internet technical standards, and the documents it publishes are called RFCs.
65%VerifiedSSE is a technology based on the HTTP protocol for server-to-client one-way real-time data stream pushing, and is the mainstream solution for streaming output from large models.
65%VerifiedIn the HTTP specification, PUT indicates a complete replacement of a resource, while PATCH indicates a partial update.
65%VerifiedIn HTTP protocol status codes, 2xx indicates success, 4xx indicates client errors, and 5xx indicates server errors.
65%VerifiedAn HTTP request message consists of three parts: the request line (method + URL + protocol version), request headers (Headers), and request body (Body).
65%UnverifiedPostman的Body格式中，form-data对应multipart/form-data，x-www-form-urlencoded对应application/x-www-form-urlencoded，raw JSON对应application/json
95%UnverifiedHTTP状态码遵循RFC 7231规范，按首位数字分为5个大类：1xx信息性响应、2xx成功、3xx重定向、4xx客户端错误、5xx服务器错误
95%UnverifiedPOST请求常见的请求体格式包括application/json、application/x-www-form-urlencoded和multipart/form-data
95%Unverifiedrunn支持HTTP/gRPC等协议的接口测试
90%UnverifiedBody格式与Content-Type声明不匹配会直接导致422或400错误
85%UnverifiedCompared to HTTP polling solutions, WebSocket can reduce invalid network requests by more than 90%.
60%UnverifiedAI agents join the game via ordinary HTTP, read a skill file, pick a name, and can start playing, with no dedicated SDK required.
50%UnverifiedThe HTTP protocol defines how browsers and servers talk to each other.
50%UnverifiedThe engineering implementation of a 'two-way channel' usually takes two forms: in-process integration (LLM call logic written into game scripts, reading and writing world state through the engine's scripting API) and out-of-process communication (the game side opens a local service or message channel such as HTTP or WebSocket, and the agent runs as a separate process requesting state and issuing commands).
50%UnverifiedAgent development is not an entirely new body of knowledge; under the hood, most agent frameworks are still HTTP requests, JSON serialization and asynchronous task scheduling.
50%UnverifiedThe 404 page is a standard status code in the HTTP protocol, indicating that the server cannot find the resource requested by the user.
50%UnverifiedHTTP compression works by the client sending an Accept-Encoding request header to declare supported compression algorithms, and if the server agrees, it returns Content-Encoding in the response header and sends compressed data.
50%