Timeline for What is the "architecture" that provides functionality to application-level URI interfaces, like chrome:// and Firefox's about:config, etc?
Current License: CC BY-SA 3.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 15, 2012 at 10:52 | comment | added | user281377 | alex gray: No. When the browser parses the string in the URL field, it recognizes the "about:" prefix and has no reason at all to use any network protocol. It's just like a command line interface. | |
| Jan 15, 2012 at 1:45 | comment | added | alex gray | lol, of course it can "do other things". i could write a screensaver that re-formats your hard drive.. but i'm wondering if the routing is being done via http, handled by a [uri protocol] (en.wikipedia.org/wiki/URI_scheme), such as Apple's URI Implementation or specific hooks / app-native "handlers"? for example chrome, the entire prefs system is within the browser viewport, and i doubt is written in the same language as the native app. | |
| Jan 15, 2012 at 0:47 | history | answered | Bryan Oakley | CC BY-SA 3.0 |