This is an automated email from the ASF dual-hosted git repository.
sijie pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/incubator-pulsar.wiki.git
The following commit(s) were added to refs/heads/master by this push:
new 0512e71 Updated PIP 21: Pulsar Edge Component (markdown)
0512e71 is described below
commit 0512e71289d81ebb84234a52ca7a961b22df3a5a
Author: Sijie Guo <[email protected]>
AuthorDate: Fri Aug 10 12:13:41 2018 -0700
Updated PIP 21: Pulsar Edge Component (markdown)
---
PIP-21:-Pulsar-Edge-Component.md | 9 ++++-----
1 file changed, 4 insertions(+), 5 deletions(-)
diff --git a/PIP-21:-Pulsar-Edge-Component.md b/PIP-21:-Pulsar-Edge-Component.md
index c89779f..ab09e39 100644
--- a/PIP-21:-Pulsar-Edge-Component.md
+++ b/PIP-21:-Pulsar-Edge-Component.md
@@ -11,8 +11,8 @@ The current Pulsar function runtime environment is located on
a Pulsar Broker in
-
-Figure 1: Current State
+
+
Therefore, it would be desirable to create a software component that provides
an environment for running Pulsar functions in a resource constrained
environment.
@@ -21,8 +21,7 @@ In the desired state, we would be able to host simple Pulsar
functions on the Io
Events can still be forwarded to the downstream Pulsar cluster for longer-term
storage, and additional Pulsar function execution.
-
-Figure 2: Desired State
+
## Requirements
@@ -44,8 +43,8 @@ The Pulsar Edge Component will wrap a standard pulsar client
object, that it wil
IoT applications would be used to capture the sensor data that is transmitted
to the ioT gateway device over short-range protocols such as ZigBee, BlueTooth,
convert it into the desired format, and publish it to the Pulsar Gateway object
using the pub/sub API.
+
-Figure 3: Pulsar Edge Component Design
