move 'future goals' section into own issues

diff --git a/Cargo.toml b/Cargo.toml
index c890bcf622cd72c1714dc9f77a3677822f4f02ec..e3273822e0671d15e73726fcfe1ca0664b03aa5b 100644 (file)
--- a/Cargo.toml
+++ b/Cargo.toml
@@ -6,7 +6,6 @@ edition = "2018"
 description = "message queue abstraction over async network streams"
 
 [workspace]
-
 members = [
     "examples/tcp-client",
     "examples/tcp-echo-server",

diff --git a/README.md b/README.md
index 224f95d024012b1cd86a45c6048d143598a91373..d7b3d03dd73c6a7c421f170a3fe4afd655864eb7 100644 (file)
--- a/README.md
+++ b/README.md
@@ -4,14 +4,6 @@ This crate provides a distributed message queue abstraction over asynchronous ne
 
 By using a message queue, crate users can focus on sending and receiving messages between clients instead of low-level networking and failure recovery.
 
-## Future Goals
-
-- Documentation
-- Connection pool (+ accounting for ordering of messages)
-- Configurable policies for handling of non-registered (unexpected) message types
-- Testing
-- Benchmarking
-
 ## Feature Status
 
 | Feature                                              | Status        |
@@ -28,7 +20,3 @@ By using a message queue, crate users can focus on sending and receiving message
 | SCTP Server                                          |               |
 | DTLS-SCTP Client                                     |               |
 | DTLS-SCTP Server                                     |               |
-| Kafka Client                                         |               |
-| RMQ Client                                           |               |
-| SQS Client                                           |               |
-| NSQ Client                                           |               |