WebFund 2013F Lecture 7 - Revision history

Sarahmathieson: /* Note */

2013-11-10T16:31:39Z

Note

← Older revision		Revision as of 16:31, 10 November 2013
Line 27:		Line 27:
	** a program calling another and passing stuff around		** a program calling another and passing stuff around
	** ie. like buttons on webpages		** ie. like buttons on webpages
	* [[File:~~http://homeostasis.scs.carleton.ca/wiki/index.php/File:Sept30~~.jpg]]		* [[File:sept30.jpg]]
	* block		* block
	** running (on a 4 core processor you could have 4 processes running simultaneously)		** running (on a 4 core processor you could have 4 processes running simultaneously)

Sarahmathieson at 21:59, 8 November 2013

2013-11-08T21:59:58Z

← Older revision		Revision as of 21:59, 8 November 2013
Line 1:		Line 1:
	Audio from the lecture given on September 30, 2013 is available [http://homeostasis.scs.carleton.ca/~soma/webfund-2013f/lectures/comp2406-2013f-lec07-30Sep2013.m4a here].		Audio from the lecture given on September 30, 2013 is available [http://homeostasis.scs.carleton.ca/~soma/webfund-2013f/lectures/comp2406-2013f-lec07-30Sep2013.m4a here].

			==Note==

			September 30

			* cookies
			** text document
			** saves info on what you were doing on site
			* stateless
			** HTTPS
			** SSH
			* what can server do to keep track of client?
			** Cookies!
			*** Something the server sets
			*** sent along later
			** Encode information in the url itself
			*** that will say what this session identifier is
			* Server can't trust anything the client sends
			* webrequests are stateless
			* How to make sure the user doesn't mess with your cookies
			** have to be encoded
			*** cookies should look like garbage
			***if you can hand edit the cookie you are doing something really dumb
			* state is being passed around in url
			* remote procedure calls
			** a program calling another and passing stuff around
			** ie. like buttons on webpages
			* [[File:http://homeostasis.scs.carleton.ca/wiki/index.php/File:Sept30.jpg]]
			* block
			** running (on a 4 core processor you could have 4 processes running simultaneously)
			** ready (waiting for a free processor)
			** waiting on I/O (blocked until something has happened)
			* synchonous I/O
			** read (b)
			** what happens here?
			*** Program went to sleep and is woken up
			*** could be doing other things here instead of giving up the CPU!
			*** Not efficient to switch between processes
			** scanf(b)
			*** only makes sense after read is completed
			* in node when you do any I/O code it returns immediately
			** asynchronous
			** callbacks solve asynchronous promblem
			*** read(s, b, callback)
			**** do the read request, and when it's done, here is the code to run encoded in this callback
			* node acts like a dispatcher
			** constantly routing data
			* classic callback in node
			** listen line
			*** has a port number + callback function

Soma at 19:09, 4 October 2013

2013-10-04T19:09:02Z

← Older revision		Revision as of 19:09, 4 October 2013
Line 1:		Line 1:
	~~==Topics==~~		Audio from the lecture given on September 30, 2013 is available [http://homeostasis.scs.carleton.ca/~soma/webfund-2013f/lectures/comp2406-2013f-lec07-30Sep2013.m4a here].

	* <tt>try</~~tt>, <tt>catch<~~/~~tt>, <tt>throw<~~/~~tt>~~

Soma: Created page with "==Topics== * `try`, `catch`, `throw`"

2013-09-26T19:09:05Z

Created page with "==Topics== * <tt>try</tt>, <tt>catch</tt>, <tt>throw</tt>"

New page

==Topics==

* <tt>try</tt>, <tt>catch</tt>, <tt>throw</tt>

WebFund 2013F Lecture 7 - Revision history

Sarahmathieson: /* Note */

Sarahmathieson at 21:59, 8 November 2013

Soma at 19:09, 4 October 2013

Soma: Created page with "==Topics== * try, catch, throw"

Soma: Created page with "==Topics== * `try`, `catch`, `throw`"