Vishal Rana - GITHUB EXTERNSHIP PROPOSAL

[VishalR3]

Application number: 5-05_Vis224_tfa_258

Full name: Vishal Rana

E-mail: vishal.ch.36@gmail.com

GitHub username: VishalR3

Prior experience:

• HTML
• CSS
• SCSS
• Tailwind CSS
• JavaScript
• TypeScript
• Vue.js
• Nuxt.js
• NestJS
• Firebase
• Prisma
• GraphQL
• PostgreSQL
• SQL
• Go lang
• React
• Next.js
• Redux
• Express.js
• Three.js

---

Proposal type:

• Existing feature request
• New feature proposal
• Refactor existing feature

Proposal title: gRPC-Web Support

Proposal description: So far, the frontend developers have had to continue to rely on JSON REST interfaces as their primary means of information exchange. But with gRPC-web, gRPC is poised to become a valuable asset for them. gRPC's support for polyglot environments, focus on performance, type safety, and developer productivity has transformed the way developers design their architectures.
It is currently impossible to implement the HTTP/2 gRPC spec in the browser, as there is simply no browser API with enough fine-grained control over the requests.

The gRPC-Web spec starts from the point of view of the HTTP/2 spec and then defines the differences. These notably include:

1. Supporting both HTTP/1.1 and HTTP/2.
2. Sending of gRPC trailers at the very end of request/response bodies as indicated by a new bit in the gRPC message header4.
3. A mandatory proxy for translating between gRPC-Web requests and gRPC HTTP/2 responses.

I want to implement gRPC-Web in Hoppscotch like swagger, to let users view message formats from .proto / URL and test the server methods by sending any messages from the Hoppscotch.

Proposal roadmap:

1. Study the Hoppscotch repo code
2. Research different ideas to implement gRPC.
3. Build UI for making gRPC Calls.
4. Implement logic for parsing proto source files and dynamic messaging
5. Implement logic for making gRPC calls.
6. Implement testing logic for gRPC.