2006/12/31, James Doc Livingston <<a href="mailto:doclivingston@gmail.com">doclivingston@gmail.com</a>>:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<span class="q">On 31/12/06, <b class="gmail_sendername">Mikkel Kamstrup Erlandsen</b> <<a href="mailto:mikkel.kamstrup@gmail.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">mikkel.kamstrup@gmail.com
</a>> wrote:</span><div><span class="q"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div><div>If an object changes uri it might as well be regarded as another object all together. The end user will see it as a rename/move but in the api I think we should go for the delete-create metafor. Meaning that the is a one-to-one correspondence between objects and uris.
<br></div></div></blockquote></span></div><br>One place where the API could be used, and is the area I'm most familiar with, is a music playing application. The search API would be useful to be able to say "give me all the user's music", rather than the "importing" step that you need to do in many music apps.
<br><br>Many music apps also hold extra metadata about the user's music (play counts, etc), and having the extra metadata lost when the user moves some files around is annoying. If the URI of something could change (and the backend implementation supported it), we could keep track of the metadata across file renames or moves.
</blockquote><div><br><br>Yeah this is a problem. I don't think it can be fixed in a good way without a real metadata server (like tracker). Unless you have a service always monitoring the files, metadata will get lost on file moves as you say.
<br><br>Apps can work around this file-moving problem without a metadata server in various ways. - Fx. storing a database of uri<->md5sum, and diff it against the music files found on each startup. Then calculate md5sums of new files and pickup metadata according to md5sums. Anyway this is not really relevant for the discussion.
<br><br>An interface spec for a metadata server is next on the list after we finish the search interface.<br> </div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Being able to do thing like that may not be worth the extra complication of URIs and objects not being one-to-one - as long as we realise we've decided that.</blockquote><div><br><br>Unless somebody come up with a real good reason I think we should settle on the uri<->object relationship.
<br> </div><br><br>Cheers,<br>Mikkel<br></div>