Hi-
As has been pointed up, we expect synchronization between local stores and
remote stores a common scenario. Having said that, we do expect to
eventually release a "server" version of WinFS. It will not solely be a
client side technology. If you think of the local WinFS storage as a local
file system, you can think about the server as a "file server" for WinFS
data.
But, we have not released any details about the WinFS server.
--
Shan Sinha [MSFT]
shans@online.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no rights
"Kent Wo" <jian_kentwo@hotmail.com> wrote in message
news:um1kdp$fGHA.2032@TK2MSFTNGP02.phx.gbl...
> It seems that "Entity Framework" and ADO.NET 3.0 related documents are
> gone from all websites... ;-)
> Is "Entity Framework" related to ObjectSpace?
>
>
> "Chris Altmann" <avalid@emailaddress.zoo> wrote in message
> news:epvCWU3fGHA.2208@TK2MSFTNGP05.phx.gbl...
>> "Kent Wo" <jian_kentwo@hotmail.com> wrote in message
>> news:OjCLRtsfGHA.2188@TK2MSFTNGP05.phx.gbl...
>>> (From business application point of view -)
>>> Will it be practical to use WinFS as object persistence layer on the
>>> server side?
>>
>> Perhaps, but there is word of a "Entity Framework" coming in ADO.Net 3.0
>> that would more likely be targeted at that.
>>
>>> Or it's just positioned to be the local cache on client side?
>>
>> It does seem that is the main focus of WinFS at this point.
>>
>> PS: I dream of a day when WinFS replaces Sharepoint, Exchange, SQL
>> Server, and file shares, both server side and client side.
>>
>>
>
>