www.pdl.cmu.edu/pNFS/archive/pnfs_reqs_mail_archive.txt::
pNFS delegated maps for distributing files over SBC, OSD and NFS storage bandwidth over memory bandwidth shows up in another statistic, machine balance
http://www.pdl.cmu.edu/pNFS/archive/pnfs_reqs_mail_archive.txtHOME |
i think it's a farily common setup to have a gigantic media library (let's say on a "media server" on the same lan as the xbox), and a small subset of the media library on the xbox, since the xbox only allows 1 hard drive (afaik). this means that xbmc users may spend a lot of time copying files back and forth to the xbox from the desktop with all the media files.
CGI Programming::
CGI::BuildForm also has the abilty to regenerate a form after the form has been submitted. I dont use CGI.pm execpt to pull the params from the users request.
http://www.perlmonks.org/index.pl?node_id=14835HOME |
it would be excellent (and probably not terribly difficult) if users could load one xml file which would display all files in a user's media library, independent of the physical location of that file. an icon of some sort would indicate whether this file is present on the xbox's hard drive or not.
(if the media server cannot be contacted, the non-local files would either be greyed out or absent from the list altogether.)
End user Zumo software developments::
that was Garmins intent by using POIs as well as the abilty to share them. If Im looking for POI files and see a CSV file, I can be 100% assured it will
http://www.zumoforums.com/index.php?topic=1409.0HOME |
if the user requests a file that's on the xbox hdd, that file is played. if the user requests a file that's not on the xbox hdd, that file is acquired automatically via the protocol of the user's choice (sftp, ftp, smb if it's supported, etc.) with a pretty percentage bar and whatnot. presumably, the last played file would be deleted off the local store if there's not enough room to acquire the file, but this should be configurable in a style similar to how tivo discards old programs when the hard drive is full.
i think this feature would provide a nice layer of abstraction between the logical notion of a "media library" and the physical hard drive on which that file is stored.
first, there's no reason "fetch" a file when today the file can just be streamed from its source.
and the intent of the database views are provide the abstration layer you are describing. you see your entire media library, regardless of where the item is located. (but, the video database views still need alot of work. they were originally designed for movies so other types of videos do not integrate well.)
 Microsoft Unleashes Visual Studio .NET
 IBM's iPhrase Buy Adds to WebSphere
|
HOME