Sean Adams
2002-01-15 22:40:17 UTC
the client struct is only for client-specific state information.
Information like this should go in a global cache, perhaps with a
pointer such as "current_track_info" from the client struct.
A while back, I was proposed a general purpose structure for
files/platlist/directories/URLs, but it was ultimately decided that things
should be referenced by their paths. To be consistent with how we access
other meta information, you should not add anything to the client struct,
but instead make a new hash indexed by the path name.
BTW I'm leaning more strongly now towards a unified "thing struct", in
light of the memory overhead of all these separate hashes.
Tiny Wireless Camera under $80!
Order Now! FREE VCR Commander!
Click Here - Only 1 Day Left!
http://us.click.yahoo.com/WoOlbB/7.PDAA/ySSFAA/rIp0lB/TM
---------------------------------------------------------------------~->
To unsubscribe from this group, send an email to:
slimp3-dev-unsubscribe-***@public.gmane.org
Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
Information like this should go in a global cache, perhaps with a
pointer such as "current_track_info" from the client struct.
A while back, I was proposed a general purpose structure for
files/platlist/directories/URLs, but it was ultimately decided that things
should be referenced by their paths. To be consistent with how we access
other meta information, you should not add anything to the client struct,
but instead make a new hash indexed by the path name.
BTW I'm leaning more strongly now towards a unified "thing struct", in
light of the memory overhead of all these separate hashes.
Great idea, Nicholas.
We already cache much of this information in individual caches that
are in the Misc.pm file. We could be a lot more efficient about
this (we have many copies of the URL/filepath, one for each hash
table.)
I just added a new cache today of the file length, it would be great
if somebody could improve this caching mechanism to be more memory
efficient and include all of the mp3info that's available.
To get started with CVS, check out the SourceForge CVS page for slimp3.
-dean
------------------------ Yahoo! Groups Sponsor ---------------------~-->We already cache much of this information in individual caches that
are in the Misc.pm file. We could be a lot more efficient about
this (we have many copies of the URL/filepath, one for each hash
table.)
I just added a new cache today of the file length, it would be great
if somebody could improve this caching mechanism to be more memory
efficient and include all of the mp3info that's available.
To get started with CVS, check out the SourceForge CVS page for slimp3.
-dean
MP3::Info has a function get_mp3info (FILE) that returns a hash of useful
information about the given mp3, including bitrate, frequency, length in
seconds and more.
As we begin to add more features to the display (such as the progress bar,
time, time remaining, bitrate, frequency, etc.) we are going to want to
retrieve this information quite often. So...
I propose adding an addition variable (a hash) to the Client structure
called 'mp3info' that will be populated when a song begins playing. All it
would require is passing the hash from get_mp3info (FILE) to the Client
structure.
I can implement this, but I don't have a CVS account (nor do I know how to
use CVS yet.) Let me know what you guys think and if you would like me to
implement this myself or if someone else wants to tackle it.
Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/information about the given mp3, including bitrate, frequency, length in
seconds and more.
As we begin to add more features to the display (such as the progress bar,
time, time remaining, bitrate, frequency, etc.) we are going to want to
retrieve this information quite often. So...
I propose adding an addition variable (a hash) to the Client structure
called 'mp3info' that will be populated when a song begins playing. All it
would require is passing the hash from get_mp3info (FILE) to the Client
structure.
I can implement this, but I don't have a CVS account (nor do I know how to
use CVS yet.) Let me know what you guys think and if you would like me to
implement this myself or if someone else wants to tackle it.
Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
Tiny Wireless Camera under $80!
Order Now! FREE VCR Commander!
Click Here - Only 1 Day Left!
http://us.click.yahoo.com/WoOlbB/7.PDAA/ySSFAA/rIp0lB/TM
---------------------------------------------------------------------~->
To unsubscribe from this group, send an email to:
slimp3-dev-unsubscribe-***@public.gmane.org
Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/