Skip to content
This repository was archived by the owner on Apr 9, 2021. It is now read-only.

Commit e08479d

Browse files
author
kkm
committed
Add empty lines strategically to keep wonky parser happy
#775 (comment) Per @carl-mastrangelo: > Add a new line between the ---, since the GitHub MD parser > is wonky.
1 parent 239f2eb commit e08479d

3 files changed

Lines changed: 3 additions & 0 deletions

File tree

_posts/2018-06-19-kotlin-project-setup.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -8,6 +8,7 @@ author-link: https://github.com/zpencer
88
company: Google
99
company-link: https://www.google.com
1010
---
11+
1112
Did you know that gRPC Java now has out of box support for Kotlin projects built with Gradle? [Kotlin](https://kotlinlang.org/) is a modern, statically typed language developed by JetBrains that targets the JVM and Android. It is generally easy for Kotlin programs to interoperate with existing Java libraries. To improve this experience further, we have added support to the [protobuf-gradle-plugin](https://github.com/google/protobuf-gradle-plugin/releases) so that the generated Java libraries are automatically picked up by Kotlin. You can now add the protobuf-gradle-plugin to your Kotlin project, and use gRPC just like you would with a typical Java project.
1213
<!--more-->
1314
The following examples show you how to configure a project for a JVM application and an Android application using Kotlin.

_posts/2018-07-13-http2_smarter_at_scale.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -8,6 +8,7 @@ author-link: https://github.com/jadekler
88
company: Google
99
company-link: https://www.google.com
1010
---
11+
1112
Much of the web today runs on HTTP/1.1. The spec for HTTP/1.1 was published in June of 1999, just shy of 20 years ago. A lot has changed since then, which makes it all the more remarkable that HTTP/1.1 has persisted and flourished for so long. But in some areas it’s beginning to show its age; for the most part, in that the designers weren’t building for the scale at which HTTP/1.1 would be used and the astonishing amount of traffic that it would come to handle. A not-so-bad case is that subsequent tests can't pass because of a leaked resource from the previous test. The worst case is that some subsequent tests pass that wouldn't have passed at all if the previously passed test had not leaked a resource.
1213
<!--more-->
1314

_posts/2018-08-20-grpc-on-http2.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -8,6 +8,7 @@ author-link: https://github.com/jadekler
88
company: Google
99
company-link: https://www.google.com
1010
---
11+
1112
In a [previous article](https://grpc.io/blog/http2_smarter_at_scale), we explored how HTTP/2 dramatically increases network efficiency and enables real-time communication by providing a framework for long-lived connections. In this article, we’ll look at how gRPC builds on HTTP/2’s long-lived connections to create a performant, robust platform for inter-service communication. We will explore the relationship between gRPC and HTTP/2, how gRPC manages HTTP/2 connections, and how gRPC uses HTTP/2 to keep connections alive, healthy, and utilized.
1213
<!--more-->
1314

0 commit comments

Comments
 (0)