Nick Pelone nickpelone

## index.html
<!doctype html>
<head>
<title>Live streaming with Strobe Media Playback</title>
<meta charset=utf-8>
<meta name=viewport content="width=device-width, user-scalable=no">
</head>
<body>

<script src="lib/swfobject.js"></script>
<script src="lib/ParsedQueryString.js"></script>

## rack_sse.ru
# rack_sse.ru
#
# An example of basic real-time, single-room broadcast chat using Server Sent
# Events in plain old Rack. This example does NOT use hijack, or the async
# hacks, it just relies on a well implemented threaded Rack server (at time of
# writing this will therefore only work with puma!). Other servers should be
# fixed to support this, as it is pretty critical to how Rack *should* work on
# most servers. The only spec-acceptable failure in this case is not flushing
# the content stream on each yield (for which the rack spec has no workaround
# today).

## create_triggers
CREATE TRIGGER person_notify AFTER INSERT OR UPDATE OR DELETE ON income
FOR EACH ROW EXECUTE PROCEDURE notify_trigger(
  'id',
  'email',
  'username'
);

CREATE TRIGGER income_notify AFTER INSERT OR UPDATE OR DELETE ON income
FOR EACH ROW EXECUTE PROCEDURE notify_trigger(
  'id',

## asciinema-upload.sh
curl -v -u $USER:$(cat ~/.config/asciinema/install-id) https://asciinema.org/api/asciicasts -F asciicast=@/path/to/demo.cast
	<!doctype html>
	<head>
	<title>Live streaming with Strobe Media Playback</title>
	<meta charset=utf-8>
	<meta name=viewport content="width=device-width, user-scalable=no">
	</head>
	<body>

	<script src="lib/swfobject.js"></script>
	<script src="lib/ParsedQueryString.js"></script>
	# rack_sse.ru
	#
	# An example of basic real-time, single-room broadcast chat using Server Sent
	# Events in plain old Rack. This example does NOT use hijack, or the async
	# hacks, it just relies on a well implemented threaded Rack server (at time of
	# writing this will therefore only work with puma!). Other servers should be
	# fixed to support this, as it is pretty critical to how Rack should work on
	# most servers. The only spec-acceptable failure in this case is not flushing
	# the content stream on each yield (for which the rack spec has no workaround
	# today).
	CREATE TRIGGER person_notify AFTER INSERT OR UPDATE OR DELETE ON income
	FOR EACH ROW EXECUTE PROCEDURE notify_trigger(
	'id',
	'email',
	'username'
	);

	CREATE TRIGGER income_notify AFTER INSERT OR UPDATE OR DELETE ON income
	FOR EACH ROW EXECUTE PROCEDURE notify_trigger(
	'id',