diff options
author | Nathan Dench <ndenc2@gmail.com> | 2019-05-24 15:16:44 +1000 |
---|---|---|
committer | Nathan Dench <ndenc2@gmail.com> | 2019-05-24 15:16:44 +1000 |
commit | 107c1cdb09c575aa2f61d97f48d8587eb6bada4c (patch) | |
tree | ca7d008643efc555c388baeaf1d986e0b6b3e28c /vendor/github.com/hashicorp/go-plugin/README.md | |
parent | 844b5a68d8af4791755b8f0ad293cc99f5959183 (diff) | |
download | terraform-provider-statuscake-107c1cdb09c575aa2f61d97f48d8587eb6bada4c.tar.gz terraform-provider-statuscake-107c1cdb09c575aa2f61d97f48d8587eb6bada4c.tar.zst terraform-provider-statuscake-107c1cdb09c575aa2f61d97f48d8587eb6bada4c.zip |
Upgrade to 0.12
Diffstat (limited to 'vendor/github.com/hashicorp/go-plugin/README.md')
-rw-r--r-- | vendor/github.com/hashicorp/go-plugin/README.md | 20 |
1 files changed, 10 insertions, 10 deletions
diff --git a/vendor/github.com/hashicorp/go-plugin/README.md b/vendor/github.com/hashicorp/go-plugin/README.md index e4558db..fe305ad 100644 --- a/vendor/github.com/hashicorp/go-plugin/README.md +++ b/vendor/github.com/hashicorp/go-plugin/README.md | |||
@@ -109,7 +109,7 @@ high-level steps that must be done. Examples are available in the | |||
109 | 1. Choose the interface(s) you want to expose for plugins. | 109 | 1. Choose the interface(s) you want to expose for plugins. |
110 | 110 | ||
111 | 2. For each interface, implement an implementation of that interface | 111 | 2. For each interface, implement an implementation of that interface |
112 | that communicates over a `net/rpc` connection or other a | 112 | that communicates over a `net/rpc` connection or over a |
113 | [gRPC](http://www.grpc.io) connection or both. You'll have to implement | 113 | [gRPC](http://www.grpc.io) connection or both. You'll have to implement |
114 | both a client and server implementation. | 114 | both a client and server implementation. |
115 | 115 | ||
@@ -150,19 +150,19 @@ user experience. | |||
150 | 150 | ||
151 | When we started using plugins (late 2012, early 2013), plugins over RPC | 151 | When we started using plugins (late 2012, early 2013), plugins over RPC |
152 | were the only option since Go didn't support dynamic library loading. Today, | 152 | were the only option since Go didn't support dynamic library loading. Today, |
153 | Go still doesn't support dynamic library loading, but they do intend to. | 153 | Go supports the [plugin](https://golang.org/pkg/plugin/) standard library with |
154 | Since 2012, our plugin system has stabilized from millions of users using it, | 154 | a number of limitations. Since 2012, our plugin system has stabilized |
155 | and has many benefits we've come to value greatly. | 155 | from tens of millions of users using it, and has many benefits we've come to |
156 | 156 | value greatly. | |
157 | For example, we intend to use this plugin system in | 157 | |
158 | [Vault](https://www.vaultproject.io), and dynamic library loading will | 158 | For example, we use this plugin system in |
159 | simply never be acceptable in Vault for security reasons. That is an extreme | 159 | [Vault](https://www.vaultproject.io) where dynamic library loading is |
160 | not acceptable for security reasons. That is an extreme | ||
160 | example, but we believe our library system has more upsides than downsides | 161 | example, but we believe our library system has more upsides than downsides |
161 | over dynamic library loading and since we've had it built and tested for years, | 162 | over dynamic library loading and since we've had it built and tested for years, |
162 | we'll likely continue to use it. | 163 | we'll continue to use it. |
163 | 164 | ||
164 | Shared libraries have one major advantage over our system which is much | 165 | Shared libraries have one major advantage over our system which is much |
165 | higher performance. In real world scenarios across our various tools, | 166 | higher performance. In real world scenarios across our various tools, |
166 | we've never required any more performance out of our plugin system and it | 167 | we've never required any more performance out of our plugin system and it |
167 | has seen very high throughput, so this isn't a concern for us at the moment. | 168 | has seen very high throughput, so this isn't a concern for us at the moment. |
168 | |||