| ActiveMac | Anonymous | Create a User | Reviews | News | Forums | Advertise |
|
|
|
User Controls |
|
New User |
|
Login |
|
Edit/View My Profile |
|
|
|
|
|
|
|
ActiveMac |
|
Articles |
|
Forums |
|
Links |
|
News |
|
News Search |
|
Reviews |
|
|
|
|
|
|
|
News Centers |
|
Windows/Microsoft |
|
DVD |
|
ActiveHardware |
|
Xbox |
|
MaINTosh |
|
News Search |
|
|
|
|
|
|
|
ANet Chats |
|
The Lobby |
|
Special Events Room |
|
Developer's Lounge |
|
XBox Chat |
|
|
|
|
|
|
|
FAQ's |
|
Windows 98/98 SE |
|
Windows 2000 |
|
Windows Me |
|
Windows "Whistler" XP |
|
Windows CE |
|
Internet Explorer 6 |
|
Internet Explorer 5 |
|
Xbox |
|
DirectX |
|
DVD's |
|
|
|
|
|
|
|
TopTechTips |
|
Registry Tips |
|
Windows 95/98 |
|
Windows 2000 |
|
Internet Explorer 4 |
|
Internet Explorer 5 |
|
Windows NT Tips |
|
Program Tips |
|
Easter Eggs |
|
Hardware |
|
DVD |
|
|
|
|
|
|
|
Latest Reviews |
|
Applications |
|
Microsoft Windows XP Professional |
|
Norton SystemWorks 2002 |
|
|
|
Hardware |
|
Intel Personal Audio Player 3000 |
|
Microsoft Wireless IntelliMouse Explorer |
|
|
|
|
|
|
|
Site News/Info |
|
About This Site |
|
Affiliates |
|
ANet Forums |
|
Contact Us |
|
Default Home Page |
|
Link To Us |
|
Links |
|
Member Pages |
|
Site Search |
|
Awards |
|
|
|
|
|
|
|
Credits |
 |
Microsoft’s Longhorn platform promises to remove middleware | |
|
||
| Time: 08:05 EST/13:05 GMT | News Source: Computer Weekly | Posted By: Joshua Baer | ||
|
Microsoft’s chief software architect Bill Gates took centre stage at last week’s software developer day in London in a bid to convince UK software developers to stick with Microsoft’s roadmap, even though Longhorn, its next generation operating system, is two to three years away. There are three pillars to Microsoft’s operating system strategy: XML, web services and managed code. According to Gates, XML will raise the capability of the Longhorn platform by providing a means whereby data can be exchanged between different systems without the need for middleware. | ||
|
Write Comment
Return to News |
Displaying 1 through 25 of 156 Last | Next |
The time now is
7:10:50 PM
ET.
Any comment problems? E-mail us |
| #1 By 1845 (67.161.212.73) at 1/30/2004 8:46:42 AM |
|
Gates said, "Of all the middleware [used today] the only one that will exist is the high-end transactional database. Everything else will be built into the operating system."
Built in != remove |
| #2 By 2459 (24.175.137.164) at 1/30/2004 9:26:50 AM |
| lol |
| #3 By 19992 (164.214.4.61) at 1/30/2004 11:33:39 AM |
|
A new file system called WinFS, based on Microsoft’s SQL Server, will allow users to organise documents based on author, project, keyword or user-defined criteria.
I wish these reporters/analysts would get it right, WinFS is not a file system, it resides above NTFS. WinFS should probably change from Windows Future Storage to WinFS Is Not a File System |
| #4 By 1845 (67.161.212.73) at 1/30/2004 5:46:16 PM |
| Ugh, not another recursive acronym! |
| #5 By 2459 (24.175.137.164) at 1/30/2004 6:35:17 PM |
|
WinFS (officially) = Windows File System
WinFS acts as a seperate relational storage system, and uses NTFS for streaming support. The current implementation uses NTFS for streaming of file-backed items mainly because NTFS already has good streaming support. WinFS is not tied to NTFS however. From WinFS newsgroups: WinFS implements a hierarchical namespace based on holding relationships between items in the WinFS item store (which is a real SQL database). That namespace constitutes folders which can point to other folders or items. Some items can be file-backed (e.g. Photo item has a corresponding ..jpg file that backs it up and that participates in metadata handling). Some items do not have any files backing them, e.g. a contact or a calendar item. All folders in WinFS are manifested via Win32 as directories. All file-backed items are surfaced as files via Win32. Its important to note here that the folders that reside in WinFS are not manifested in NTFS at all. The entire WinFS namespace is mastered in WinFS and not in NTFS. Streams corresponding to file-backed items are actually stored in NTFS and thats an implementation detail. The fact that filestreams are stored in NTFS is not exposed to end-users or applications. In fact we would discourage any application to depend on this fact at all. We want users and applications to use the UNC namespace \\machinename\StoreName\... to access content in their WinFS stores even thought the streams corresponding to all file-backed items reside in c:\System Volume Information\... Sanjay Anand (VIP) |
| #6 By 19992 (68.69.127.19) at 1/30/2004 7:43:38 PM |
|
#4 We could always go with TTP for 'The Ttp Project' :)
#5 When did they rename Windows Future Storage to Windows File System? Also, why would they? It's not a file system. WinFS is a service, a rather nice and extravagant one, that resides on top of the NTFS core. The actual Longhorn system files will not reside within WinFS, they will sit inside of a NTFS space on the same drive, same partition, etc. NTFS will continue to manage and incorporate files. Doesn't sound like a seperate file system to me. Although, you may elect not to run WinFS at all. You can install Longhorn using Fat32, although, if you do, you may not use WinFS. |
| #7 By 2459 (24.175.137.164) at 1/30/2004 10:53:06 PM |
|
Various MS employees, including Bill G, have referred to WinFS as "Windows File System" for a while now (since a bit before PDC at least). Also the documentation from the Longhorn SDK and the online material at MSDN refers to it the same way.
Note that by RTM, the name could change, because MS had a survey for developers to choose names for the various platform components. http://msdn.microsoft.com/Longhorn/understanding/pillars/WinFS/default.aspx?pull=/library/en-us/dnaero/html/wux_topic_storage.asp |
| #8 By 2459 (24.175.137.164) at 1/30/2004 10:57:25 PM |
|
Further Info on WinFS from the SDK:
http://longhorn.msdn.microsoft.com/lhsdk/winfs/conwinfsfilesystem.aspx http://longhorn.msdn.microsoft.com/lhsdk/winfs/daovrWelcomeToWinFS.aspx and an MS employee's blog: http://anopinion.net/category/2.aspx This post was edited by n4cer on Friday, January 30, 2004 at 22:58. |
| #9 By 12071 (203.217.66.106) at 1/31/2004 12:56:36 AM |
|
"Gates said, "We are fudging the line between the client and the server." When the speed of the network is taken into consideration, he said, "It will be possible to run the client PC in a stateless way," where user data and applications move back and forth between a network server and desktop PC running Longhorn."
Isn't this just Sun's Network PC idea just done many many years later when bandwidth is less of an issue? Sorry to sound cynical, but if this IS the case, then I can already heard the drums of "innovation" beating again. |
| #10 By 2459 (24.175.137.164) at 1/31/2004 6:10:42 AM |
|
There are a few differences.
Sun's idea involved replacing the PC with dumb terminals, having everything done on the server(s), including data storage, and shifting the majority of costs to managing a few servers. With Longhorn, MS is pushing rich client more than ever, but with apps that can use the network and web services seamlessly (Smart Clients) so that there isn't as much of a seperation between using data or app elements that are local and those on the network, or a large difference in app functionality when in a disconnected state versus a connected state. There is a push for increased availability of user data for sharing and synchronization, but, except in some enterprise or service provider cases, this involves using the client PC to host the data. Probably the closest thing that comes to thin client in MS' offerings (besides web apps) are No-touch and ClickOnce deployed, zero-impact client applications. Though these applications still require limited storage on the client computer, and local processing power. I guess you could get closer to Sun's vision if all apps were deployed to a server (in the home user case, this would still be their regular PC) and had users log in via terminal services. Longhorn will bring TS closer to the local client experience. |
| #11 By 1845 (67.161.212.73) at 1/31/2004 12:49:13 PM |
|
happyguy - Microsoft never called WinFS Windows Future Storage. That was a dream of Paul T. Microsoft folks have always called it Windows File System.
Not a file system? Well, in one way it isn't. In another way, it's an abstraction layer (that serves, stores, indexes, etc. files) on top of NTFS. Though NTFS is a component (or dependency depending on your point of view), I think it is still valid to call it a file system. Still, I can see your point that. I've heard that WinFS is only a codename anyway, so it may simply be called Windows Storage or something like that by the time it gets released. chris, I don't think this is like Sun's or Oracle's dumb terminal concept. I think Microsoft's idea revolves around peer to peer servers. In some scenarios (like browsing the web, authenticating to your domain controller, etc.) it's a client. In others (streaming your personal photos, music, tv, etc. to other rooms in your house) it's a server. I think Microsoft has already begun this path with lite versions of IIS and MSDE for non server OSes. |
|
Write Comment
Return to News |
Displaying 1 through 25 of 156 Last | Next |
The time now is
7:10:50 PM
ET.
Any comment problems? E-mail us |
