Will winfs be used instead of database (in some certain scenarios)?

Hi,



I just installed WinFS beta and took a quick look at those samples. Since I
have been developing .NET smart client application for a couple of years, I
can imagine WinFS can be used as a local storage for offline data, and I
assume in many scenarios that'll be a better choice than MSDE. My question
is, what about the server side? Currently most business applications use
relational databases to store data, will it be possible that some of (at
what percentage?) those applications will use WinFS on the server side
instead to store data like purchase order item etc? (If the answer is yes)
If something needs to be used to bridge the gap between database and WinFS,
will it be ObjectSpace?



Thanks

Kent

I suspect writing a WinFS sync adapter to sync between a local WinFS store
and an existing remote relational database will be a popular option.

"Kent Wo" <jian_kentwo@hotmail.com> wrote in message
news:OMdKXxffGHA.4080@TK2MSFTNGP03.phx.gbl...
> Hi,
>
>
>
> I just installed WinFS beta and took a quick look at those samples. Since
> I have been developing .NET smart client application for a couple of
> years, I can imagine WinFS can be used as a local storage for offline
> data, and I assume in many scenarios that'll be a better choice than MSDE.
> My question is, what about the server side? Currently most business
> applications use relational databases to store data, will it be possible
> that some of (at what percentage?) those applications will use WinFS on
> the server side instead to store data like purchase order item etc? (If
> the answer is yes) If something needs to be used to bridge the gap between
> database and WinFS, will it be ObjectSpace?
>
>
>
> Thanks
>
> Kent
>
>

(From business application point of view -)
Will it be practical to use WinFS as object persistence layer on the server
side?
Or it's just positioned to be the local cache on client side?

Thanks
Kent

"Chris Altmann" <avalid@emailaddress.zoo> wrote in message
news:%23gByYkqfGHA.4792@TK2MSFTNGP03.phx.gbl...
>I suspect writing a WinFS sync adapter to sync between a local WinFS store
>and an existing remote relational database will be a popular option.
>

"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.

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.
>
>

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.
>>
>>
>
>

So, will you talk about this WinFS server thing in the coming TechEd? ;-)
Back to the original question - what I'm interested in is that if WinFS
(server) will play a role as business application server side data storage
or persistence layer...
But according to what Chris said, it sounds like ASP.NET 3.0 and 'entity
framework' would be a better candidate for that role...

Hopefully we can have more detail about all those stuffs after TechEd...

Thanks
Kent

"Shan Sinha [MSFT]" <shans@online.microsoft.com> wrote in message
news:u7YjucIgGHA.4940@TK2MSFTNGP05.phx.gbl...
> 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.
>>>
>>>
>>
>>
>
>