Confirmed users
971
edits
No edit summary |
(→Cons) |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
== Unencrypted Data on the Firefox Home Servers == | |||
== Unencrypted Data | |||
The most ideal setup for us is to be able to do a sync session from the Firefox Home servers directly to the Sync Servers. Just like any other sync client would. This means that we run a sync session and store the unencrypted records on our own servers. This allows us to easily put a web service on top of those and to run online and offline queries on the user's data. | The most ideal setup for us is to be able to do a sync session from the Firefox Home servers directly to the Sync Servers. Just like any other sync client would. This means that we run a sync session and store the unencrypted records on our own servers. This allows us to easily put a web service on top of those and to run online and offline queries on the user's data. | ||
| Line 7: | Line 5: | ||
=== Pros === | === Pros === | ||
* We have access to unencrypted data, which means we can prepare | * We have access to unencrypted and normalized sync data, which means we can easily query it, prepare results offline and do full text search on the server | ||
* This is a simple setup, we just need to run a sync client and database servers to store the unencrypted data | * This is a simple setup, we just need to run a sync client and database servers to store the unencrypted data | ||
| Line 32: | Line 30: | ||
* Have to maintain multiple code bases for multiple platforms (C++, Objective-C, C#, Java) | * Have to maintain multiple code bases for multiple platforms (C++, Objective-C, C#, Java) | ||
* Not all platforms have a solid webview/native-code bridge (Like iOS) | * Not all platforms have a solid webview/native-code bridge (Like iOS) | ||
* This is not a web application | |||
== Crypto and Storage in the Browser == | == Crypto and Storage in the Browser == | ||