windows phone 7 - Azure, Sync Framework and Access Control Service: Are there obvious shortcomings or problems in using this technologies together? -

i have desktop application uses flat files (some xml , small pictures) data. want data available on other pcs have desktop application installed , usable smartphone client (wp7 @ moment) well.

the user should have easy synchronize data. should able use accounts possesses (live-login, googlemail, facebook,...).

i thought using azure blob storage save data in azure, sync framework perform actual synchronization , access control service handle authentication.

i have not used of technologies before advice great i'm searching foremost errors or shortcomings in strategy don't see yet. approach viable @ all?

windows azure virtualized datacentre. elaborate , complicated , pitched @ corporations don't want own server infrastructure or hardware.

if understand correctly, want cloud fileserver, not whole lan. windows skydrive fulfils requirement nicely , offers 25gb of storage per member no charge membership.

about hotmail , windows live people confuse hotmail , windows live, because when set hotmail account uses windows live authentication , therefore end windows live account , associated facilities, including skydrive. however, entirely possible set windows live account using any email address username.

if this, important aware windows live password associated given email address independent of password required mail server hosts mail account. can cause great deal of user confusion. hotmail (or other mail server uses windows live authentication) guaranteed same password.

there no official microsoft framework support skydrive. there is open source project called skydriveapiclient, works full .net framework. tried porting author bit of architecture astronaut, , absolutely riddled [serializable] not available on wp7x.

the wp7 guys have said wp7 framework include support skydrive not in mango (wp7.1) , given microsoft's typical release cycle 18 months , mango has yet hit streets, i'd 2 years before can count on intrinsic cloud file services wp7.

roll-your-own wouldn't hard, wcf services dead easy use wp7. that's not cloud since have provide , maintain server infrastructure yourself. reason , given ms timetable, have put great deal of effort producing own skydrive client wp7. core functionality complete , refactoring, improving robustness , adding performance enhancements local cacheing of tokens (cookies, essentially). don't intend release it; have number of apps planned depend on functionality , suits me fine there substantial barrier competition.

i didn't tell tease you. point i'm sure skydrive right answer put lot of work making happen.

• cloud file storage perfect fit mobile devices.
• azure not answer sort of phone apps individuals want because data store isn't shared in way required indexing or supports high levels of concurrency
• i can think of corporate phone apps benefit using sql server storage
• azure can file services represents ongoing expense. nobody's going put when google , microsoft both give away web based cloud storage.
• i can attest if you're determined, possible use skydrive wp7.
• cloud storage way you're going programmatically accessible storage that's shared user's mobile device , computer. 1 of things intend depends on shared storage write silverlight app lets prepare map routes multiple waypoints on desktop computer , companion app uses them on wp7.

---

the windows live team has released call support wp7. supply sample project showing how instantiate browser object , load login pages , manipulate them log in , use javascript api manipulate skydrive.

this has 1 big advantage: browser cookies , cached credentials. disadvantages obvious; technical shortcomings notwithstanding windows live team seems think thing people want phone tag photos , fiddle social media.

i have finished own libraries. not support of social media twaddle. have treated skydrive no more or less cloud file system, providing

• authenticate(username, password)
• createfolder(folderpath[, blocking=false])
• delete(fileorfolderpath[, blocking=false])
• savestring(filepath, value[, blocking=false])
• loadstring(filepath)

i handle binaries convert.tobase64 makes unnecessary , strings convenient xml. createfolder, delete , savestring optionally blocking. loadstring blocking because it's function returns loaded string. createfolder recursive can create entire path in 1 call (eg /folder1/folder2/folder3). calling createfolder on pre-existing path has no effect, , savestring uses createfolder ensure path valid, making unnecessary create filepath in advance. authenticate loads file system (except file content) memory eliminating server chatter. asynchronous , filesystemready event announces when file system loaded. model maintained add , remove files , folders.

this lot of work , no 1 reponded attempt make open source project i'm not inclined give fruits of labour away, provided plans don't compete mine persuaded come arrangement.