768638 - (metro-sync) [Tracking] Sync enhancements for Windows 8 Metro

Status: RESOLVED INVALID

(Firefox for Metro Graveyard :: General, defect)

Description

[Jim Mathies [:jimm]]

In a metro recent meeting we discussed solving the problem of synced profile data between metrofx and firefox. The original idea was to share a profile but this was thrown out for technical reasons. So we decided to investigate using the sync service, either remotely or possibly through the creation of a local sync server that mimics the remote protocol allowing both browsers to stay in sync pretty much in real time.

Filing this bug to kick off that discussion.

Comment 1

[Gregory Szorc [:gps]]

This is probably best discussed in a medium with more interactivity than Bugzilla. Want to try pinging us in #sync?

I think what we (the Sync team) will want to know initially is the basic architecture of metrofx so we can assess the options.

Comment 2

[Jim Mathies [:jimm]]

(In reply to Gregory Szorc [:gps] from comment #1)
> This is probably best discussed in a medium with more interactivity than
> Bugzilla. Want to try pinging us in #sync?
> 
> I think what we (the Sync team) will want to know initially is the basic
> architecture of metrofx so we can assess the options.

Sure I'll drop in. To answer your question, it's basically firefox with a different front end. The two browsers install in the same location, use the same runtime and stub exe. They'll just load up different front ends a few different backend components, most notably a different widget implementation.

The key here for sync is timing, we'd like data such as bookmarks, passwords, cookies and other critical data sets to be in sync at all times. Another interesting challenge is the runtime model, while firefox on the desktop always runs the metro browser is suspended whenever it's not in use.

Comment 3

[Jim Mathies [:jimm]]

bug 769424 is about using networked sync to keep data synchronized. This is presumed to be a temporary solution since we want to avoid reliance on the network (if we can) to accomplish this. Morphing this bug appropriately.

Comment 4

[Richard Newman [:rnewman]]

Jim, did you accidentally un-morph this bug?

Comment 5

[Jim Mathies [:jimm]]

(In reply to Richard Newman [:rnewman] from comment #4)
> Jim, did you accidentally un-morph this bug?

Not sure, un-morph from what? I think this is basically a dupe of bug 769424 now since sync 2.0 is the new local sync, and I'm sure there are bugs filed on that someplace.