4 ms·
He, unfortunately, didn't disambiguate between example.com/foo/bar/baz, foo.example.com/bar/baz, etc. so it's unclear. It is kind of amusing to think of the en
by zackbloom 10y ago
He, unfortunately, didn't disambiguate between example.com/foo/bar/baz, foo.example.com/bar/baz, etc. so it's unclear.
It is kind of amusing to think of the entire Internet as a giant directory though.
- thaumasiotes 10y ago> It is kind of amusing to think of the entire Internet as a giant directory though. How else would you think about it?
- krapp 10y agoA distributed operating system, with the URL being a shell command sent to some remote application. The resemblance between a URL and a directory path is becoming an anachronism anyway, as: GET http://example.com/foo/bar/baz might as well be return com.example.foo(bar, baz) more often then than not.
- thaumasiotes 10y agoI don't understand the distinction you're trying to draw. On a personal machine, a directory path might look like /usr/bin/vi whereas a command would look like /usr/bin/vi. Command invocations require you to identify what command you want. So we provide locations.
- krapp 10y agoMy point is that a URL is often an abstraction of an invocation of a function or class with segments and query parameters mapping to methods or arguments, and that it doesn't need to have any relationship to file paths on the server, despite superficially looking like a file path.
- jacquesm 10y ago> A distributed operating system, with the URL being a shell command sent to some remote application. All too often URLs really do allow you to issue shell commands (or raw SQL), even today!