Archive:Drive Mapping: Difference between revisions
>Malloc No edit summary |
>Malloc No edit summary |
||
| Line 14: | Line 14: | ||
This is where we store file temporarily. It's not shared between users/instances/runs. Very volatile.<br/><br/> | This is where we store file temporarily. It's not shared between users/instances/runs. Very volatile.<br/><br/> | ||
U = No idea what to call this<br/> | U = No idea what to call this<br/> | ||
Store mutable data here which doesn't belong to any user. Is there anything we need besides profiles.xml?<br/><br/> | Store mutable data here which doesn't belong to any user. Is there anything we need besides profiles.xml? Should this be writable by scripts or only xbmc itself?<br/><br/> | ||
P = profiles<br/> | P = profiles<br/> | ||
Give some default profile to begin with, can create more profiles. If some file doesn't exist in here, read from Q. On write, copy from Q and make changes.<br/><br/> | Give some default profile to begin with, can create more profiles. If some file doesn't exist in here, read from Q. On write, copy from Q and make changes.<br/><br/> | ||
New names<br/> | |||
Currently we support Windows like drive mappings. This is only because of the xbox, and moving forward we would like to change this to a protocol string (system://) or an environment variable (ENV[system]). Proposed names:<br/> | |||
Q -> system:// | |||
Z -> temp:// | |||
P -> profile:// or user:// | |||
U -> global://? Do we really need this? It should only be writable by the app itself. | |||
Revision as of 22:34, 2 July 2008
Proposed drive mappings
Currently:
U = UserData
Q = System (should not be writable)
P = Profile
Z = Temporary
T = ?
Proposal:
Q = system
This is where we install stuff, it never changes (except on update), it's not writable
Z = Temporary
This is where we store file temporarily. It's not shared between users/instances/runs. Very volatile.
U = No idea what to call this
Store mutable data here which doesn't belong to any user. Is there anything we need besides profiles.xml? Should this be writable by scripts or only xbmc itself?
P = profiles
Give some default profile to begin with, can create more profiles. If some file doesn't exist in here, read from Q. On write, copy from Q and make changes.
New names
Currently we support Windows like drive mappings. This is only because of the xbox, and moving forward we would like to change this to a protocol string (system://) or an environment variable (ENV[system]). Proposed names:
Q -> system://
Z -> temp://
P -> profile:// or user://
U -> global://? Do we really need this? It should only be writable by the app itself.