This gist shows how to create a GIF screencast using only free OS X tools: QuickTime, ffmpeg, and gifsicle.
To capture the video (filesize: 19MB), using the free "QuickTime Player" application:
<!DOCTYPE html> | |
<html> | |
<head> | |
<title>Leaflet</title> | |
<link rel="stylesheet" href="http://cdn.leafletjs.com/leaflet-0.3.1/leaflet.css" /> | |
<script src="http://cdn.leafletjs.com/leaflet-0.3.1/leaflet.js"></script> | |
<script src="http://maps.google.com/maps/api/js?v=3.2&sensor=false"></script> | |
<script src="http://matchingnotes.com/javascripts/leaflet-google.js"></script> | |
</head> | |
<body> |
#!/usr/bin/python | |
# Rewrite URL Script for Secure Web Issue | |
# author: Kaan Yamanyar | |
from Crypto.Cipher import DES | |
from datetime import datetime, timedelta | |
import sys | |
import re | |
import base64 | |
def parseToken(str): |
protected String encrypt(String token) throws Exception { | |
// Instantiate the cipher | |
final SecretKeySpec key = new SecretKeySpec("oldhouse".getBytes("ISO-8859-1"), "DES"); | |
AlgorithmParameterSpec paramSpec = new IvParameterSpec("houseold".getBytes()); | |
Cipher cipher = Cipher.getInstance("DES/CFB8/NoPadding"); | |
cipher.init(Cipher.ENCRYPT_MODE, key, paramSpec); | |
byte[] binaryData = cipher.doFinal(token.getBytes("ISO-8859-1")); | |
return new String(org.apache.commons.codec.binary.Base64.encodeBase64(binaryData), "ISO-8859-1"); |
This year marks the first year that we are doing full scale rendering of our SPA application on our mobile.walmart.com Node.js tier, which has provided a number of challenges that are very different from the mostly IO-bound load of our prior #nodebf.
The infrastructure outlined for last year is the same but our Home, Item and a few other pages are prerendered on the server using fruit-loops and hula-hoop to execute an optimized version of our client-side JavaScript and provide a SEO and first-load friendly version of the site.
To support the additional CPU load concerns as peak, which we hope will be unfounded or mitigated by our work, we have also taken a variety of steps to increase cache lifetimes of the pages that are being served in this manner. In order of their impact:
Over the last couple months we noticed some community stagnation and big performance issues with DocPad. Because of that, and few other problems that appeared to be far from being solved, we decided to move to a new stack #109.
For backward compatibility purposes, we decided to keep all folders and all automated task commands with the exact same name.
New features should be expected in upcoming versions, this release is intended to be a 1:1 mapping.