Archive:Drive Mapping: Difference between revisions

@@ Line 1: / Line 1: @@
-Proposed drive mappings<br/>
-<br/>
-Currently:<br/>
-U = UserData<br/>
-Q = System (should not be writable)<br/>
-P = Profile<br/>
-Z = Temporary<br/>
-T = ?<br/>
-<br/>
-Proposal:<br/>
-Q = system<br/>
-This is where we install stuff, it never changes (except on update), it's not writable<br/><br/>
-Z = Temporary<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/>
-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/>
-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://<br/>
-Z -> temp://<br/>
-P -> profile:// or user://<br/>
-U -> global://? Do we really need this?  It should only be writable by the app itself.<br/>

Latest revision as of 00:22, 10 April 2012