{"id":1320,"date":"2004-08-27T00:00:00","date_gmt":"2004-08-27T00:00:00","guid":{"rendered":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2004\/08\/27\/winfs-axed-from-longhorn-client-and-server\/"},"modified":"2021-12-30T11:39:09","modified_gmt":"2021-12-30T11:39:09","slug":"winfs-axed-from-longhorn-client-and-server","status":"publish","type":"post","link":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2004\/08\/27\/winfs-axed-from-longhorn-client-and-server\/","title":{"rendered":"WinFS Axed From Longhorn Client and Server"},"content":{"rendered":"<p>Microsoft announced, as expected, that it is cutting some of its planned Longhorn features in order to get the desktop version of the product out the door by 2006.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>The Windows File System (WinFS) &#8212; technology that was set to simplify information storage and retrieval &#8212; won&#8217;t make it into the final, shipping versions of Longhorn client, company officials confirmed.<\/p>\n<p>Longhorn is still slated to include both the Indigo and Avalon subsystems, contrary to some rumors to the contrary over the past couple of days.  And Microsoft is still expecting to deliver as part of Longhorn updated &#8220;fundamental&#8221; application-programming interfaces providing core power management, driver management, application installation\/deployment, digital rights management and other basic tasks.<\/p>\n<p>http:\/\/www.microsoft-watch.com\/article2\/0,1995,1640454,00.asp<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3],"tags":[],"class_list":["post-1320","post","type-post","status-publish","format-standard","hentry","category-product"],"_links":{"self":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/1320","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/comments?post=1320"}],"version-history":[{"count":1,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/1320\/revisions"}],"predecessor-version":[{"id":3807,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/1320\/revisions\/3807"}],"wp:attachment":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/media?parent=1320"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/categories?post=1320"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/tags?post=1320"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}