Confirmed users
385
edits
User:Anaaktgeboren/SearchEngineSync: Difference between revisions
→Spec
(→Spec) |
(→Spec) |
||
| Line 100: | Line 100: | ||
** default engine OpenSearch objects will not be sync'ed, as these are hardcoded and already present on the machines. However their entries in the search db will synced as this contains the user generated ordering & keywords. | ** default engine OpenSearch objects will not be sync'ed, as these are hardcoded and already present on the machines. However their entries in the search db will synced as this contains the user generated ordering & keywords. | ||
** on the fence about whether to sync Sherlock objects in 1.0, or iterate on that later if anyone screams | ** on the fence about whether to sync Sherlock objects in 1.0, or iterate on that later if anyone screams | ||
** on the fence about whether to sync extension shipped plugins, especially given Asa's concern about hijacking & the avg funny business | ** on the fence about whether to sync extension shipped plugins, especially given Asa's concern about hijacking & the avg funny business, though searchservice will consider an extension shipped plugin as a default in _isDefault() | ||
** the currently selected engine will not be synced, as that is a local setting and probably does not make sense to sync | ** the currently selected engine will not be synced, as that is a local setting and probably does not make sense to sync | ||
** read-only engines cannot be serialized, and therefore probably should not be sync'ed (I believe this is just the default ones) | ** read-only engines cannot be serialized, and therefore probably should not be sync'ed (I believe this is just the default ones) | ||