From cf24894fb9b71f5670b771e7f55f94185cbcf32d Mon Sep 17 00:00:00 2001
From: Martyn Welch <martyn.welch@collabora.com>
Date: Thu, 22 Apr 2021 11:15:10 +0100
Subject: [PATCH] Move data sharing to architecture section
The data sharing document is more of a architectural overview of how
data sharing is expected to be handled on Apertis. Move it to the
architecture section.
Signed-off-by: Martyn Welch <martyn.welch@collabora.com>
---
content/{concepts => architecture}/data_sharing.md | 0
content/concepts/egress_filtering.md | 8 ++++----
2 files changed, 4 insertions(+), 4 deletions(-)
rename content/{concepts => architecture}/data_sharing.md (100%)
diff --git a/content/concepts/data_sharing.md b/content/architecture/data_sharing.md
similarity index 100%
rename from content/concepts/data_sharing.md
rename to content/architecture/data_sharing.md
diff --git a/content/concepts/egress_filtering.md b/content/concepts/egress_filtering.md
index e0ec7c0f9..379afd067 100644
--- a/content/concepts/egress_filtering.md
+++ b/content/concepts/egress_filtering.md
@@ -166,7 +166,7 @@ bundle does so.
access](#application-without-direct-internet-access).
- The application bundle should not be allowed to pass messages to
other application bundles via inter-process communication mechanisms
- such as those described in [Data sharing]( {{< ref "/concepts/data_sharing.md" >}} ).
+ such as those described in [Data sharing]( {{< ref "data_sharing.md" >}} ).
- Applications which require IPC for their normal functionality
are outside the scope of this scenario, and are described in
[Application without direct Internet
@@ -192,7 +192,7 @@ access](#application-without-direct-internet-access).
Android also does not support preventing its equivalents of our [Content
hand-over]( {{< ref "/concepts/content_hand-over.md" >}} ) and [communication with public
-interfaces]( {{< ref "/concepts/data_sharing.md" >}} ): any application can declare a
+interfaces]( {{< ref "data_sharing.md" >}} ): any application can declare a
custom *intent* (analogous to our public interfaces), and any
application can register to receive implicit intents matching a pattern
(analogous to our content hand-over). Again, this is more similar to our
@@ -339,7 +339,7 @@ browser or navigation application is performed.
Suppose the address book app requires the ability to communicate with
apps/agents that implement a [public
-interface]( {{< ref "/concepts/data_sharing.md" >}} ) for its normal functionality: for
+interface]( {{< ref "data_sharing.md" >}} ) for its normal functionality: for
example, it might have a button to perform a device-wide search for
files and other content items that mention a contact's name.
@@ -400,7 +400,7 @@ flag](https://developer.android.com/reference/android/Manifest.permission.html#I
Applications without that flag are not allowed to open network sockets,
and can only communicate with the Internet via mechanisms analogous to
our [Content hand-over]( {{< ref "/concepts/content_hand-over.md" >}} ) and [Data
-sharing]( {{< ref "/concepts/data_sharing.md" >}} ).
+sharing]( {{< ref "data_sharing.md" >}} ).
However, iOS does not appear to support this scenario, as described in
[Purely offline application](#purely-offline-application).
--
GitLab