Skip to content

Instantly share code, notes, and snippets.

Avatar
🏠
Working from home

Prithviraj Billa Prithvirajbilla

🏠
Working from home
View GitHub Profile
@Prithvirajbilla
Prithvirajbilla / fix_github_https_repo.sh
Created Jul 2, 2018 — forked from m14t/fix_github_https_repo.sh
Convert HTTPS github clones to use SSH
View fix_github_https_repo.sh
#/bin/bash
#-- Script to automate https://help.github.com/articles/why-is-git-always-asking-for-my-password
REPO_URL=`git remote -v | grep -m1 '^origin' | sed -Ene's#.*(https://[^[:space:]]*).*#\1#p'`
if [ -z "$REPO_URL" ]; then
echo "-- ERROR: Could not identify Repo url."
echo " It is possible this repo is already using SSH instead of HTTPS."
exit
fi
@Prithvirajbilla
Prithvirajbilla / http_streaming.md
Created Aug 20, 2018 — forked from CMCDragonkai/http_streaming.md
HTTP Streaming (or Chunked vs Store & Forward)
View http_streaming.md

HTTP Streaming (or Chunked vs Store & Forward)

The standard way of understanding the HTTP protocol is via the request reply pattern. Each HTTP transaction consists of a finitely bounded HTTP request and a finitely bounded HTTP response.

However it's also possible for both parts of an HTTP 1.1 transaction to stream their possibly infinitely bounded data. The advantages is that the sender can send data that is beyond the sender's memory limit, and the receiver can act on