2010/6/13 Mikkel Kamstrup Erlandsen mikkel.kamst...@gmail.com:
I think that MostUsedDirectories is not what we want. I was assuming it
would be Most/LeastRecentOrigin and Most/LeastPopularOrigin.
Well, again, I believe origin as what it is now (ie. dirname(uri))
should not be exposed in the API
You are assuming that the URIs have a tree-like syntax, which is not
true in general. What if we dropped file:/// and http:// URIs altogether
and used Tracker UUIDs all the way?
Also the download use case we discussed numerous times - If we say that
Origin is where the user was at the event time
I dont think using Tracker UUIDs would make sense atm This will generate
a dependency...
However we could use our own UUIDs but it will require a change the the DB
schema
On Sun, Jun 13, 2010 at 11:46 PM, Mikkel Kamstrup Erlandsen
mikkel.kamst...@gmail.com wrote:
You are assuming that the
2010/6/13 Mikkel Kamstrup Erlandsen mikkel.kamst...@gmail.com:
You are assuming that the URIs have a tree-like syntax, which is not
true in general. What if we dropped file:/// and http:// URIs altogether
and used Tracker UUIDs all the way?
We always need a URI, so that the application has
4 matches
Mail list logo
