maxenglander

programs:
  - name: audit-log-start-latency
    metrics:
      histograms:
        - name: function_latency_seconds
          help: Latency of Linux kernel function
          table: dist
          bucket_type: fixed
          bucket_keys:
            - 1000     # 1ms

maxenglander

test1 test2

maxenglander

Test

Test 2

hello world!

maxenglander

Topics

1. Installing Node.js on Mac OS X with Brew
2. How does the Node.js search path work?
3. How do I decide whether to install something locally or globaly?
4. Look at OSC code
5. Look at Andy Hall's Photoshop code
6. Bare minimum Photoshop plugin

Installing Node.js on Mac OS X with Brew

maxenglander

//-----------------------------------------------------------------
// EGR 126 fall 2012
// Student Name: Rebecca Brenneis
// Assignment: A4
// Submission Date: 9/23/12
// ----------------------------------------------------------------
// 

#include <iostream> // required for cin, cout, edl.
#include <cmath> // required for sqrt()

maxenglander

 
#include <iostream> // required for cin, cout, edl.
#include <cmath> // required for sqrt()
 
Int main()
{
 
//Declare objects and
double x1, y1, x2, y2, side1, side2, distance;
side1 = x2 –x1;

maxenglander

A traditional request handling model works like this:

1. Browser makes a connection (think of it as dialing a restaurant)
2. Server accepts the connection (restaurant employee answers phone)
3. Browser sends a request (think of this as saying "I'd like to make a dinner reservation")
4. Server processes the request and sends the response ("Got it, your reservation is made")
5. The connection is closed (both sides hang up)

This is great, except that each employee is expensive, and the restaurant can only afford to pay N employees. If there are more people calling in a given moment than their are employees to respond to a call, callers will get frustrated that nobody has picked up, hang up, and try again later (or try another restaurant).

maxenglander

A traditional request handling model works like this:

1. Browser makes a connection (think of it as dialing a restaurant)
1. Server accepts the connection (restaurant employee answers phone)
1. Browser sends a request (think of this as saying "I'd like to make a dinner reservation")
1. Server processes the request and sends the response ("Got it, your reservation is made")
1. The connection is closed (both sides hang up)

This is great, except that each employee is expensive, and the restaurant can only afford to pay N employees. If there are more people calling in a given moment than their are employees to respond to a call, callers will get frustrated that nobody has picked up, hang up, and try again later (or try another restaurant).

maxenglander

.my_highlight {
  text-decoration:underline;
  background-color:orange;
}

maxenglander

{}