「responses」の検索結果

Architecture-level decisions for putting a CDN in front of a web app's static assets, API responses, and file/media delivery: provider selection (hyperscaler vs. specialist $/GB), signed-URL / tokenized access for gating private content at the edge, cache invalidation strategy (versioned URLs vs. purge APIs), origin shield / tiered caching for high-miss-rate content, and CDN-layer geo-restriction. Use when deciding which CDN to put in front of a new or growing service, when private/paywalled files need edge delivery without an origin round-trip per request, or when purge/invalidation behavior is being designed rather than debugged. NOT for HTTP cache-control header syntax, Vary, stale-while-revalidate, or surrogate-key purge mechanics (see `cdn-cache-control-headers`); NOT for Cloudflare-specific product configuration once Cloudflare is already chosen (see `cloudflare`); NOT for video-specific transcoding, adaptive bitrate ladders, or streaming-protocol packaging (see `managed-video-streaming-pipeline`).

日本語の概要は準備中です。原文の説明を表示しています。

Automatically intercepts and optimizes prompts using the prompt-learning MCP server. Learns from performance over time via embedding-indexed history. Uses APE, OPRO, DSPy patterns. Activate on "optimize prompt", "improve this prompt", "prompt engineering", or ANY complex task request. Requires prompt-learning MCP server. NOT for simple questions (just answer them), NOT for direct commands (just execute them), NOT for conversational responses (no optimization needed).

日本語の概要は準備中です。原文の説明を表示しています。