>----------
>WinFS Storage
> WinFS provides T-SQL views of the Item tables, with one view per item type. To
>enforce the security of the store and the consistency of the data, the data can
>only be read through the views and can only be modified using stored procedures.
>For example, the following line will return the requested information for all
>tracks in the Media Library on your machine:
>SELECT Artist, Title, Album FROM Audio.[Track!V1]
>Some objects contain references to other objects. For example, a Track object
>has a member called Authors, which is a collection of Author objects, each of
>which has a DisplayName property, which gives the name of an artist who authored
>the track. It is possible to construct a query for all of the tracks that are
>attributed to a particular artist, which you can cross-reference to your
>personal address book to see if you have the cell phone number of any artist for
>which you have a track. (This assumes, of course, that you have a
>celebrity-filled address book!)
> Not everyone is a database developer and able to construct complicated select
>queries, so WinFS provides several higher-level APIs to make inserting,
>deleting, and querying for items simpler.
>
>----------
>
>So it seems they are using SQL Server as some sort of massive storage, which
>utilises metadata attached to each 'file'/Record to perform searches, as well as
>for inserting, deleting,updating. I'm wondering though how slow the OS will be
>with legacy applications (oh gods...everything we run now will be a 'legacy'
>app) since there would have to be an abstraction layer in between to translate
>old file system calls to the new WINFS format.
>This just...seems...like...'BLOAT'....^_^
>
>-Gel
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
