|
|
|
|
|
|
by Aydarbek
153 days ago
|
|
|
Yes, that maps quite naturally. Classic HTTP Range is byte-oriented, but custom range units (e.g. `Range: offsets=…`) or using `Link` headers for pagination both fit log semantics well. I kept the initial API explicit (`offset` / `limit`) to stay obvious for curl users, but offset-range via headers is something I want to experiment with, especially if it helps generic tooling. |
|
|