1) WinFS client creates a StorageContext within which all interactions with
the store are managed. This StorageContext is bound to a store and hence
the transaction by design can not span multiple stores. It will be
interesting to hear your scenarios that benefit from this. Could you please
pen them down?
2) Yes your observation is spot on. One of the biggest uses of TxF will be
for Windows update to provide atomicity assurances during software updates.
However, app installation where code is installed in WinFS is not a WinFS
scenario. Type installation is the aspect of app installation that affects
WinFS - these types are installed on a per store basis. I am certain you
have some scenarios in mind, please share it with us.
3) This is a very large discussion particularly in the context of Search
alignment efforts with Vista that WinFS is undertaking as part of its Beta2.
The short summary is that, we will leverage Vista (Windows Desktop Search)
for full text search on WinFS. The redundancy concern you observed below
was one of the primary motives behind this change. Please stay tuned on the
WinFS blogs for more info on this.
thanks for your interest!
Simon Skaria [MSFT] email@example.com
This posting is provided "AS IS" with no warranties, and confers no rights
"RE66" <RE66@discussions.microsoft.com> wrote in message
> 1. Does WinFS will support transaction which cross two differant stores on
> the same machine (Not a network drive).
> 2. One major benefit of transactional FS will be simplfy writting
> installation application and undo installation. If 1 is false then the
> usafullness of WinFS will be significantly reduce.
> 3. Does Windows Desktop Search API (part of Vista ) will be included in
> WinFS API therefore creating redundant API ?