X-Git-Url: https://gerrit.automotivelinux.org/gerrit/gitweb?a=blobdiff_plain;f=docs%2F4_APIs_and_Services%2F4.5_Message_Signaling%2F4_AGL_Service_Signal_Composer%2F1_Architecture.md;fp=docs%2F4_APIs_and_Services%2F4.5_Message_Signaling%2F4_AGL_Service_Signal_Composer%2F1_Architecture.md;h=0000000000000000000000000000000000000000;hb=eefc3ab6cbb8a5901632f46d99e13c8d90b2415d;hp=62c2f0fa7a6c5098bcad310a8d72eb3e9f8444ce;hpb=4aad369c9728061c97b3de792286e743ee884b09;p=AGL%2Fdocumentation.git

diff --git a/docs/4_APIs_and_Services/4.5_Message_Signaling/4_AGL_Service_Signal_Composer/1_Architecture.md b/docs/4_APIs_and_Services/4.5_Message_Signaling/4_AGL_Service_Signal_Composer/1_Architecture.md
deleted file mode 100644
index 62c2f0f..0000000
--- a/docs/4_APIs_and_Services/4.5_Message_Signaling/4_AGL_Service_Signal_Composer/1_Architecture.md
+++ /dev/null
@@ -1,73 +0,0 @@
----
-edit_link: ''
-title: Architecture presentation
-origin_url: >-
-  https://git.automotivelinux.org/apps/agl-service-signal-composer/plain/docs/part-1/1-Architecture.md?h=master
----
-
-<!-- WARNING: This file is generated by fetch_docs.js using /home/boron/Documents/AGL/docs-webtemplate/site/_data/tocs/apis_services/master/agl-service-signal-composer-developer-guides-api-services-book.yml -->
-
-# Signal Composer
-
-## Architecture
-
-Here is a quick picture about the signaling architecture :
-
-![GlobalArchitecture]
-
-Key here are on both layers, **low** and **high**.
-
-- **Low levels** binding used as _AGL service_, handle data exchange protocol to
- decode/encode and retransmit with an AGL compatible format using **Application
- Framework** events. These are divided into two parts, which are :
-  - A transport Layer binding's plug-in that is able to read/write from a device.
-  - Decoding/Encoding parts that expose signals.
-- **High level signal composer** binding gathers multiple **low level** signaling
- sources. Then from these sources, it exposes theirs **raw** signals or more interesting
- can creates new virtuals signals from them. Example:
- A signal made from gps latitude and longitude that computes the heading of
- vehicle. This is modular and each signal source should be handled by specific
- plugins which take care of get the underlying event from **low level** or
- define signaling composition with simple or complex operation to output value
- from **raw** signals.
-
-A transport plug-in is a shared library that shares a common API to be
-compatible with **low level** services that is:
-
-- **open/close**: method to open a handle which could be a socket, file or
- device by example.
-- **read/write**: method to read and write a stream of data.
-
-Configuration is made by sending a special packet using a write method to the
-handle. In brief, this could be compared to the layer 1 and 2 of [OSI model].
-
-There are three main parts with **Signal Composer**:
-
-- Configuration files which could be splitted in differents files. That will
- define:
-  - metadata with name of **signal composer** api name
-  - additionnals configurations files
-  - plugins used if so, **low level** signals sources
-  - signals definitions
-- Dedicated plugins
-- Signal composer API
-
-## Terminology
-
-Here is a little terminology guide to set the vocabulary:
-
-- **api**: a binding API name
-- **action**: a function called at a certain time
-- **callbacks**: a function called at a certain time
-- **event**: the raw event that materialize the signal
-- **plugins**: a C/C++ code with functions that be called by signal composer
- service
-- **sources**: an external binding API that generate signals for the signal
- composer service
-- **signals**: an event generated by the **Application Framework**
-- **virtual signals**: a signal composed of **raw signals** with value
- calculated by a **callbacks**
-- **raw signals**: an event generated by a **low level** binding
-
-[OSI model]: https://en.wikipedia.org/wiki/OSI_model
-[GlobalArchitecture]: pictures/Global_Signaling_Architecture.png "Global architecture"