It's a fantastic day for digital monks! I just wish the url took a searchable ?query=aristotle on load so you could add it to your browser's search engine list
Yeah, there has been a discussion on that matter. It would take the same time as the entire bootstrapping and the search query processing to open such an URL. This is doable but may exhibit inadequate performance.
I support you, though, that independent of the search time it is valuable to have a linking standard like that.
Anchor does not solve the bootstrapping issue. You may click an URL with an anchor or without, but the new page in the browser will need to load the database fragment and search over it before showing you the retrieved record. There's no faster way known yet in this implementation.
Comments
It's a fantastic day for digital monks! I just wish the url took a searchable ?query=aristotle on load so you could add it to your browser's search engine list
Yeah, there has been a discussion on that matter. It would take the same time as the entire bootstrapping and the search query processing to open such an URL. This is doable but may exhibit inadequate performance.
I support you, though, that independent of the search time it is valuable to have a linking standard like that.
Wouldn't #query=Aristotle work and be just as fast?
The databases still needs to bootstrap first, then the code can search on it. Initialization phase should prepend showing a record.
Sure, that's why the anchor would be faster, because you can use the same initialization code and still accept the query in the URL.
Anchor does not solve the bootstrapping issue. You may click an URL with an anchor or without, but the new page in the browser will need to load the database fragment and search over it before showing you the retrieved record. There's no faster way known yet in this implementation.