mirror of
https://github.com/refraction-networking/utls.git
synced 2025-04-04 12:37:35 +03:00
crypto/tls: fix typo in cacheEntry godoc
Change-Id: Idcea184a5b0c205efd3c91c60b5d954424f37679 Reviewed-on: https://go-review.googlesource.com/c/go/+/460540 Run-TryBot: Tobias Klauser <tobias.klauser@gmail.com> Reviewed-by: Filippo Valsorda <filippo@golang.org> Reviewed-by: Heschi Kreinick <heschi@google.com> Reviewed-by: Ian Lance Taylor <iant@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Auto-Submit: Tobias Klauser <tobias.klauser@gmail.com>
This commit is contained in:
parent
5661b3ddeb
commit
a076513123
1 changed files with 1 additions and 1 deletions
2
cache.go
2
cache.go
|
@ -27,7 +27,7 @@ type cacheEntry struct {
|
||||||
// to the certificate in the cache is decremented. Once the number of references
|
// to the certificate in the cache is decremented. Once the number of references
|
||||||
// reaches zero, the entry is evicted from the cache.
|
// reaches zero, the entry is evicted from the cache.
|
||||||
//
|
//
|
||||||
// The main difference between this implmentation and CRYPTO_BUFFER_POOL is that
|
// The main difference between this implementation and CRYPTO_BUFFER_POOL is that
|
||||||
// CRYPTO_BUFFER_POOL is a more generic structure which supports blobs of data,
|
// CRYPTO_BUFFER_POOL is a more generic structure which supports blobs of data,
|
||||||
// rather than specific structures. Since we only care about x509.Certificates,
|
// rather than specific structures. Since we only care about x509.Certificates,
|
||||||
// certCache is implemented as a specific cache, rather than a generic one.
|
// certCache is implemented as a specific cache, rather than a generic one.
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue