rdoursenaud

#!/usr/bin/env python2.7
# encoding=utf8
#
# Copyright 2007 Google Inc.
# Copyright 2016 Raphaël Doursenaud
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#

kassim

import android.content.Context;
import android.content.res.TypedArray;
import android.graphics.Typeface;
import android.support.design.widget.TextInputLayout;
import android.util.AttributeSet;
import android.view.View;
import android.view.ViewGroup;
import android.widget.EditText;

import uk.co.chrisjenx.calligraphy.CalligraphyConfig;

CMCDragonkai

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

ego008

# -*- coding: utf-8 -*-

"""
  Example of how to use Poster.encode on AppEngine.
     http://atlee.ca/software/poster/

  The only variation needed versus the example from Poster is that
  GAE's UrlFetch cannot use the generator returned by multipart_encode()
  for payload, so simply create a payload string first.
"""

martinsik

$(function () {
    "use strict";

    // for better performance - to avoid searching in DOM
    var content = $('#content');
    var input = $('#input');
    var status = $('#status');

    // my color assigned by the server
    var myColor = false;