| import React, { useState } from "react"; | |
| import { | |
| format, | |
| startOfWeek, | |
| addDays, | |
| startOfMonth, | |
| endOfMonth, | |
| endOfWeek, | |
| isSameMonth, | |
| isSameDay, |
| const videoPlayer = netflix | |
| .appContext | |
| .state | |
| .playerApp | |
| .getAPI() | |
| .videoPlayer; | |
| // Getting player id | |
| const videoPlayer = videoPlayer | |
| .getAllPlayerSessionIds()[0] |
sudo apt-get install nghttp2 libnghttp2-dev
http://curl.haxx.se/download/curl-7.46.0.tar.bz2
tar -xvjf curl-7.46.0.tar.bz2
cd curl-7.46.0
./configure --with-nghttp2 --prefix=/usr/local
make
sudo make install
sudo ldconfig
| /** | |
| * Filters an array of objects using custom predicates. | |
| * | |
| * @param {Array} array: the array to filter | |
| * @param {Object} filters: an object with the filter criteria | |
| * @return {Array} | |
| */ | |
| function filterArray(array, filters) { | |
| const filterKeys = Object.keys(filters); | |
| return array.filter(item => { |
| bower install --save PolymerElements/iron-elements | |
| bower install --save PolymerElements/paper-elements | |
| bower install --save PolymerElements/gold-elements | |
| bower install --save PolymerElements/neon-elements | |
| bower install --save PolymerElements/platinum-elements | |
| bower install --save GoogleWebComponents/google-web-components |
To make this work in CSS:
background: url('images.svg#chart');or img:
<img src="images.svg#chart">
This page provides a full overview of PHP's SessionHandler
life-cycle - this was generated by a set of test-scripts, in order to provide an exact overview of when and
what you can expect will be called in your custom SessionHandler implementation.
Each example is a separate script being run by a client with cookies enabled.
To the left, you can see the function being called in your script, and to the right, you can see the resulting calls being made to a custom session-handler registed using session_set_save_handler().
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
| <?php | |
| $codes = [ | |
| 'ab' => 'Abkhazian', | |
| 'aa' => 'Afar', | |
| 'af' => 'Afrikaans', | |
| 'ak' => 'Akan', | |
| 'sq' => 'Albanian', | |
| 'am' => 'Amharic', | |
| 'ar' => 'Arabic', |