RFC 10008 Introduces QUERY HTTP Method for Complex, Safe API Searches

·1 views

A new HTTP method called QUERY was formally standardized in RFC 10008 in June 2026, addressing a long-standing workaround in API design. Developers have traditionally used POST requests to send complex search filters as JSON payloads, but this obscured whether the operation was safe or state-changing. QUERY fills this gap by allowing a request body like POST while retaining the safe, idempotent, and cacheable semantics associated with read-only operations like GET. This distinction matters because HTTP intermediaries such as proxies, caches, and gateways use the method token to reason about a request before inspecting application logic. The new method is expected to improve clarity in API contracts and enable better caching and retry behavior for complex query operations.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Twilio Launches Official MCP Server to Link AI Agents with SMS, Voice, and Chat

Twilio has released an official Model Context Protocol (MCP) server that allows AI tools like Claude, Cursor, and Windsurf to interact with Twilio's communications platform using natural language commands. The server enables AI agents to send and receive SMS, MMS, and WhatsApp messages, manage voice calls, and access delivery logs and billing metrics without manual API calls. Credentials are stored locally in the user's environment, keeping API keys secure while the server handles authentication. The integration is particularly suited for use cases such as automated alert systems, OTP testing, and customer support workflows where speed and reduced manual intervention are priorities. Developers can install the server via npm and configure it through a JSON settings file using their Twilio account credentials.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

AWS Offers Three Distinct AI Security Architectures for Different Operational Needs

AWS security teams can choose from three AI-assisted architectures depending on their workflow: AWS Managed MCP for live, interactive investigation by engineers; Custom MCP for analyzing pre-approved security reports stored in S3; and Lambda combined with boto3 and Bedrock for scheduled, automated report generation. Each pattern is suited to a specific operational context — live triage, report analysis, or backend automation — and using them interchangeably introduces risk and inefficiency. AWS Managed MCP, delivered via the AWS Agent Toolkit, allows AI coding agents like Claude Code and Codex to access live AWS services such as Security Hub, GuardDuty, and Inspector through read-only IAM roles. Custom MCP, by contrast, does not require broad live API access and instead works against approved report artifacts already saved in S3. The core principle is that production reporting pipelines should not depend on an analyst's presence, while interactive investigation should not be forced into a scheduled batch job.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Developer Open-Sources Game Backend Before the Game Itself Exists

A developer has released DWCS (Distributed World Computation & Synchronization), an open-source networking backend built for a multiplayer VR game still in early planning stages. Rather than letting the code sit unused, the developer cleaned it up and published it as a standalone, engine-agnostic infrastructure project. DWCS handles distributed task coordination and shared world-state synchronization without any knowledge of game logic, physics, or engine-specific systems. The project was motivated by a desire to explore a balanced approach to computation in multiplayer systems, avoiding the cost pitfalls of server-heavy models and the trust issues of client-heavy ones. By separating the backend from the game itself, the developer aims to make the infrastructure reusable for any application needing distributed state synchronization.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Experiment Tests Whether AI Coding Agents Track Base Commits Under Parallel Execution

A black-box experiment on MonkeyCode SaaS examines how parallel AI coding agent tasks handle version consistency when both originate from the same base commit. Two simultaneous tasks — one editing authentication code, another editing logging — are run while an unrelated human commit is pushed mid-session to test for silent base substitution. The experiment checks whether each agent's output patch correctly identifies its base commit, remains isolated to its allowed file scope, and produces consistent results regardless of the order patches are applied. A key concern is that silently swapping a task's base commit without notice is flagged as an unacceptable behavior, while explicit conflicts or requests to rerun from the new base are considered acceptable outcomes. The author, a self-disclosed MonkeyCode user with no project affiliation, frames parallel agent sessions as a data consistency challenge rather than merely a performance feature.

0 comments Read more at DEV Community