So... speaking as a software engineer who hasn't looked into the architecture (so I could be really off base): The problem is that the artwork scan is too deeply connected. Make it a separate "product" (i.e. data/process hiding). All the artwork scan needs to know is the sizes to cache and how to hand the data (pointer to a file? blob?) over when requested. Want to make the hand-over more efficient? Have the art scan request a "handle" for each track (don't try to mangle a name (or however it's currently done) the current way, but hide data in that direction as well. This is basic stuff, based on the fact that engineers are human and can only manage so many things at once, Split a problem into smaller pieces and they can be attacked severally - and you have a better chance of success.
-- bobkoure ------------------------------------------------------------------------ bobkoure's Profile: http://forums.slimdevices.com/member.php?userid=14646 View this thread: http://forums.slimdevices.com/showthread.php?t=69894 _______________________________________________ discuss mailing list discuss@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/discuss
