From 51b2ee5e2aecc92deca3d93e56e93e7a7b3ea6bd Mon Sep 17 00:00:00 2001 From: David Seifert Date: Sat, 25 Nov 2017 23:14:21 +0100 Subject: dev-java/jetty-alpn-api: [QA] Consistent whitespace in metadata.xml --- dev-java/jetty-alpn-api/metadata.xml | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) (limited to 'dev-java') diff --git a/dev-java/jetty-alpn-api/metadata.xml b/dev-java/jetty-alpn-api/metadata.xml index d0ea9f190876..e7ff4b83b664 100644 --- a/dev-java/jetty-alpn-api/metadata.xml +++ b/dev-java/jetty-alpn-api/metadata.xml @@ -8,7 +8,9 @@ eclipse/jetty.alpn.api - The Jetty project provides an implementation of the TLS extension for ALPN for OpenJDK 7 and OpenJDK 8. ALPN allows the application layer to negotiate which protocol to use over the secure connection. + + The Jetty project provides an implementation of the TLS extension for ALPN for OpenJDK 7 and OpenJDK 8. ALPN allows the application layer to negotiate which protocol to use over the secure connection. -Any protocol can be negotiated by ALPN within a TLS connection. The protocols that are most commonly negotiated are HTTP/2 (for browsers that support it) and, historically, SPDY. The ALPN implementation is therefore not HTTP/2 or SPDY specific in any way. Jetty's ALPN implementation, although hosted under the umbrella of the Jetty project, is independent of Jetty (the Servlet Container); you can use the ALPN implementation in any other Java network server. + Any protocol can be negotiated by ALPN within a TLS connection. The protocols that are most commonly negotiated are HTTP/2 (for browsers that support it) and, historically, SPDY. The ALPN implementation is therefore not HTTP/2 or SPDY specific in any way. Jetty's ALPN implementation, although hosted under the umbrella of the Jetty project, is independent of Jetty (the Servlet Container); you can use the ALPN implementation in any other Java network server. + -- cgit v1.2.3-65-gdbad