Re:Claude Advanced Tool Use
by johnfn on Monday November 24, 2025 @05:02PM
(#46039928)
Really? Hmm... where in the HTTP spec does it allow for returning an arbitrary subset of any specific request, rather than the whole thing? And where does it ensure all the results are keyed by id so that you can actually build and update a sensible cache around all of it rather than the mess that totally free-form HTTP responses lead to? Oh weird HTTP doesn't have any of that stuff? Maybe we should make a new spec, something which does allow for these patterns and behaviors? And it might be confusing if we use the exact same name as HTTP, since the usage patterns are different and it enables new abilities. If only we could think of such a name...
[ Parent
| on HN ]
An HTTP Range request asks the server to send parts of a resource back to a client. Range requests are useful for various clients, including media players that support random access, data tools that require only part of a large file, and download managers that let users pause and resume a download.
https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/Ran...
also handy for bypassing bandwidth restrictions: capped at 100kbps? launch 1000 workers to grab chunks then assemble the survivors
that's what axel downloader does!
HTTP Range doesn't have anything to do with allowing a client to select a subset of fields.
The Range header isn't for requesting a subset of a resource from the server?
Let's say your REST endpoint returned an object with keys foo, bar, baz and quuz. How would you use HTTP Range to only select foo and baz?
Re:Claude Advanced Tool Use
by tlarkworthy on Monday November 24, 2025 @05:46PM
(#46040315)
Etag and cache control headers?