You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pekko.apache.org by fa...@apache.org on 2023/08/04 16:06:44 UTC

[incubator-pekko-grpc] branch main updated: fix link in README.md (#128)

This is an automated email from the ASF dual-hosted git repository.

fanningpj pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/incubator-pekko-grpc.git


The following commit(s) were added to refs/heads/main by this push:
     new 1ca1a56a fix link in README.md (#128)
1ca1a56a is described below

commit 1ca1a56affb93b64c98059f935b1a792c352a874
Author: PJ Fanning <pj...@users.noreply.github.com>
AuthorDate: Fri Aug 4 17:06:39 2023 +0100

    fix link in README.md (#128)
---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 60b67172..21087a13 100644
--- a/README.md
+++ b/README.md
@@ -18,7 +18,7 @@ The API on both sides (Client and Server) is a simple Pekko Streams-based one.
 
 The client side is
 currently implemented on top of [io.grpc:grpc-netty-shaded](https://mvnrepository.com/artifact/io.grpc/grpc-netty-shaded),
-we plan to replace this by just [io.grpc:grpc-core](https://mvnrepository.com/artifact/io.grpc/grpc-core) and @extref[Pekko HTTP](pekko-http:).
+we plan to replace this by just [io.grpc:grpc-core](https://mvnrepository.com/artifact/io.grpc/grpc-core) and [Pekko HTTP](https://pekko.apache.org/docs/pekko-http/current/).
 
 As for performance, we are currently relying on the JVM TLS implementation,
 which is sufficient for many use cases, but is planned to be replaced with


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@pekko.apache.org
For additional commands, e-mail: commits-help@pekko.apache.org