This is an automated email from the ASF dual-hosted git repository.
jerrypeng pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/pulsar.wiki.git
The following commit(s) were added to refs/heads/master by this push:
new 25970a1 Updated PIP 46: Next gen Proxy (markdown)
25970a1 is described below
commit 25970a1c14fb3800a9b2c2ddeee1ff5c13ddf1d6
Author: Boyang Jerry Peng <jerry.boyang.p...@gmail.com>
AuthorDate: Wed Oct 16 12:36:41 2019 -0700
Updated PIP 46: Next gen Proxy (markdown)
---
PIP-46:-Next-gen-Proxy.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/PIP-46:-Next-gen-Proxy.md b/PIP-46:-Next-gen-Proxy.md
index bb3a64a..9929cc9 100644
--- a/PIP-46:-Next-gen-Proxy.md
+++ b/PIP-46:-Next-gen-Proxy.md
@@ -10,7 +10,7 @@ Currently the proxy is used simply to forward messages to
brokers but it has the
**Initial design goals:**
-* Support different methods to publish and consume such as via http
+* Support different methods to publish and consume such as via HTTP/REST
* Support different wire protocol from other messaging/streaming systems. For
example, allowing users to use Apache Kafka producers and consumers to be able
to produce and consume messages from an Apache Pulsar cluster. When can support
a wide variety of wire protocols but I think we should prioritize the following
ones:
1. Apache Kafka
2. MQTT
