website: make performance impact explicit for connect-native

I was going to the public feedback on Connect-Native app integration and came across [this](https://twitter.com/relistan/status/1012263110403555329) thread. Added a few statements in the Connect-Native app integration page.
This commit is contained in:
Anubhav Mishra 2018-06-29 17:35:58 -07:00 committed by GitHub
parent a6069aae77
commit 4b5efe7464
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 5 additions and 3 deletions

View File

@ -10,9 +10,11 @@ description: |-
Applications can natively integrate with the Connect API to support Applications can natively integrate with the Connect API to support
accepting and establishing connections to other Connect services without accepting and establishing connections to other Connect services without
the overhead of a [proxy sidecar](/docs/connect/proxies.html). This page the overhead of a [proxy sidecar](/docs/connect/proxies.html). This option
will cover the high-level overview of integration, registering the service, is especially useful for applications that may be experiencing performance issues
etc. For language-specific examples, see the sidebar navigation to the left. with the proxy sidecar deployment. This page will cover the high-level overview
of integration, registering the service, etc. For language-specific examples,
see the sidebar navigation to the left.
Connect is just basic mutual TLS. This means that almost any application Connect is just basic mutual TLS. This means that almost any application
can easily integrate with Connect. There is no custom protocol in use; can easily integrate with Connect. There is no custom protocol in use;