DistOS 2015W Session 2 - Revision history

Jasons: /* Reading Response Discussion */

2015-04-20T09:07:56Z

Reading Response Discussion

← Older revision		Revision as of 09:07, 20 April 2015
Line 1:		Line 1:
	= Reading Response Discussion =		= Reading Response Discussion =
			*In computing, time-sharing, is the sharing of a computing resource among many users by means of multiprogramming and multi-tasking.
			**In the old days, computers were expensive and physically large, so one computer was shared among many users using terminals.


	== Mother of All Demos: ==		== Mother of All Demos: ==

Abeinges: /* Discussion: Easy on one computer, hard on multiple computers */

2015-04-06T04:36:36Z

Discussion: Easy on one computer, hard on multiple computers

← Older revision		Revision as of 04:36, 6 April 2015
Line 67:		Line 67:
	\|-		\|-
	! Why is it easy?		! Why is it easy?
			\|
	* Full control of all software		* Full control of all software
	* All possible users are physically co-located		* All possible users are physically co-located
	* Latency minimized		* Latency minimized
	! Why is it hard?		! Why is it hard?
			\|
	* Games are fundamentally low-latency. Networking is fundamental high-latency.		* Games are fundamentally low-latency. Networking is fundamental high-latency.
	* Input prediction doesn't work well on twitchy games.		* Input prediction doesn't work well on twitchy games.

Abeinges: /* Discussion: Easy on one computer, hard on multiple computers */

2015-04-06T04:36:00Z

Discussion: Easy on one computer, hard on multiple computers

← Older revision		Revision as of 04:36, 6 April 2015
Line 67:		Line 67:
	\|-		\|-
	! Why is it easy?		! Why is it easy?
			* Full control of all software
			* All possible users are physically co-located
			* Latency minimized
	! Why is it hard?		! Why is it hard?
			* Games are fundamentally low-latency. Networking is fundamental high-latency.
			* Input prediction doesn't work well on twitchy games.
			* Have to handle lying or faulty clients.
			* Have to handle users finding each other.
	\|-		\|-
	\|}		\|}

Aimbot: Aimbot moved page DistOS 2014W Session 2 to DistOS 2015W Session 2: Wrong year

2015-01-14T21:55:32Z

Aimbot moved page DistOS 2014W Session 2 to DistOS 2015W Session 2: Wrong year

← Older revision	Revision as of 21:55, 14 January 2015
(No difference)

Aimbot: /* Professor lead discussion 1 */ Updated time sharing definition.

2015-01-14T03:15:49Z

Professor lead discussion 1: Updated time sharing definition.

← Older revision		Revision as of 03:15, 14 January 2015
Line 42:		Line 42:
	You'll find in the history of trying to achieve this dream of a distributed operating system there has always been a road block as a result of a technical issue. People would come up with a solution to this technical issue but then they would find that some other technical issue would crop up. For example 'The Mother of All Demos' tried to build a distributed operating system but they had no networking. They had to point a television camera at the computer monitor to be able to demo their concept. The early internet came along and dealt with the issue of no networking. However the early internet itself had other technical issues.		You'll find in the history of trying to achieve this dream of a distributed operating system there has always been a road block as a result of a technical issue. People would come up with a solution to this technical issue but then they would find that some other technical issue would crop up. For example 'The Mother of All Demos' tried to build a distributed operating system but they had no networking. They had to point a television camera at the computer monitor to be able to demo their concept. The early internet came along and dealt with the issue of no networking. However the early internet itself had other technical issues.

	A common buzz word during the early days of development was '''~~Time Sharing~~'''~~. Time sharing~~ is ~~about the sharing of resources between users~~. ~~Today~~ the ~~concept of~~ time ~~sharing is similar~~ to sharing a ~~processor between multiple~~ processes.		A common buzz word during the early days of development was '''time sharing''', which is an old term for multiple processes running simultaneously. However, at the time it referred to multiple users sharing the CPU cycles on a single computer. Today, a single user's many processes using a single CPU is much more common.

	= Discussion: Easy on one computer, hard on multiple computers =		= Discussion: Easy on one computer, hard on multiple computers =

Aimbot: /* Mother of All Demos: */ Minor updates, clarifications

2015-01-14T03:09:38Z

Mother of All Demos:: Minor updates, clarifications

← Older revision		Revision as of 03:09, 14 January 2015
Line 3:		Line 3:
	== Mother of All Demos: ==		== Mother of All Demos: ==

	Team: Jason, Kirill, Sravan, Agustin, Hassan Ambalica, Apoorv, Khaled		'''Team:''' Jason, Kirill, Sravan, Agustin, Hassan Ambalica, Apoorv, Khaled

	* 1968, Doug Inglebard		* 1968, lead by Doug Inglebard
	* One computer with multiple terminals ~~controlling~~		* Initial public display of many modern technologies
			* One computer with multiple remote terminals
	* Video conferencing		* Video conferencing
	* Computer mouse		* Computer mouse (and coined the term)
	* Word processing, rudimentary copy and paste		* Word processing, rudimentary copy and paste
	* Dynamic file linking		* Dynamic file linking (hypertext)
	* Revision control/version control/source control		* Revision control/version control/source control
	* Collaborative real-time editor		* Collaborative real-time editor
	** User privilege control in that user can provide read-only access, read-write privilege to file		** User privilege control in that user can provide read-only access, read-write privilege to file
	* ~~Cord~~ keyboard		* Corded keyboard
	** Marco keyboard that allows messages quickly, while using mouse at same time		** Marco keyboard that allows messages quickly, while using mouse at same time
	* Not really a distributed operating system, but great start because multiple users at different terminals could share same resources		* Not really a distributed operating system, but great start because multiple users at different terminals could share same resources

Aimbot: /* Alto */ Clarifications, minor updates

2015-01-14T03:03:52Z

Alto: Clarifications, minor updates

← Older revision		Revision as of 03:03, 14 January 2015
Line 22:		Line 22:
	== Alto ==		== Alto ==

	Team: Tory, Veena, Sameer, Mert, Deep, Nameet, Moe		'''Team:''' Tory, Veena, Sameer, Mert, Deep, Nameet, Moe

	* 1973		* Initially developed around 1973 by Xerox, upgraded over next few years
	* High speed (3 Mbps @ 1km ~~difference~~)		* High speed network connectivity (3 Mbps @ 1km distance)
	* ~~Connects~~ up to 256 machines		* Connected up to 256 machines
	* Protocol similar to cross between UDP/TCP, before TCP invented		* Protocol similar to cross between UDP/TCP, before TCP invented
	* Allowed sharing printers		* Allowed sharing of printers
	* Also allowed ~~for distributing~~ files across computers (redundancy/reliability)		* Also allowed distribution of files across computers (redundancy/reliability)
	* Sort of early cloud		* Sort of early cloud
	* Allowed for remote debugging, store error logs		* Allowed for remote debugging, store error logs
	* Allowed machines to use processing power of others		* Allowed machines to use processing power of others
	* ~~much~~ of the time it would be ~~doing nothing~~		* Much of the time it would be idling, which is amazing at a time when computers cost a fortune


	= Professor lead discussion 1 =		= Professor lead discussion 1 =

Hassansaid: /* Discussion: Easy on one computer, hard on multiple computers */

2015-01-13T02:01:03Z

Discussion: Easy on one computer, hard on multiple computers

← Older revision		Revision as of 02:01, 13 January 2015
Line 62:		Line 62:
	\|-		\|-
	\|}		\|}

			{\| class="wikitable" width="100%"
			\|+ '''Mortal Kombat/Twitch Gaming'''
			\|-
			! Why is it easy?
			! Why is it hard?
			\|-
			\|}

			{\| class="wikitable" width="100%"
			\|+ '''Photo Album'''
			\|-
			! Why is it easy?
			! Why is it hard?
			\|-
			\|}

			=== Commonalities ===
			* Synchronization
			* Bandwidth
			* Reliability/Fault Tolerance
			* Interoperability
			* Discovery
			* Routing
			** In modern system this issue has been mostly abstracted away
			** Classic example would be Wireless Ad-hoc networking

			The above list is not hard on a single system because all the cores have equal access to all the resources. Also as a result of excellent engineering modern single systems can very effective deal with any errors that may result.

Hassansaid: /* Reading Response Discussion */

2015-01-13T01:54:40Z

Reading Response Discussion

← Older revision		Revision as of 01:54, 13 January 2015
Line 34:		Line 34:
	* Allowed machines to use processing power of others		* Allowed machines to use processing power of others
	* much of the time it would be doing nothing		* much of the time it would be doing nothing


			= Professor lead discussion 1 =

			A true distributed operating system does not actually exist, its more of a dream.

			You'll find in the history of trying to achieve this dream of a distributed operating system there has always been a road block as a result of a technical issue. People would come up with a solution to this technical issue but then they would find that some other technical issue would crop up. For example 'The Mother of All Demos' tried to build a distributed operating system but they had no networking. They had to point a television camera at the computer monitor to be able to demo their concept. The early internet came along and dealt with the issue of no networking. However the early internet itself had other technical issues.

			A common buzz word during the early days of development was '''Time Sharing'''. Time sharing is about the sharing of resources between users. Today the concept of time sharing is similar to sharing a processor between multiple processes.

			= Discussion: Easy on one computer, hard on multiple computers =

			{\| class="wikitable" width="100%"
			\|+ '''Instant Messaging'''
			\|-
			! Why is it easy?
			! Why is it hard?
			\|-
			\| Can't be out sync
			\| Synchronization issues
			* Server-client modal
			** If two or more servers they get requests same time, they have to figure out how to synchronize the data
			* Peer-to-Peer
			** Each peer has to figure out how to sync each message
			\|-
			\| Only one data store/source
			\|-
			\|}

Hassansaid: /* Reading Response Discussion */

2015-01-13T01:30:38Z

Reading Response Discussion

← Older revision		Revision as of 01:30, 13 January 2015
Line 1:		Line 1:
	== Reading Response Discussion ==		= Reading Response Discussion =

			== Mother of All Demos: ==

			Team: Jason, Kirill, Sravan, Agustin, Hassan Ambalica, Apoorv, Khaled

			* 1968, Doug Inglebard
			* One computer with multiple terminals controlling
			* Video conferencing
			* Computer mouse
			* Word processing, rudimentary copy and paste
			* Dynamic file linking
			* Revision control/version control/source control
			* Collaborative real-time editor
			** User privilege control in that user can provide read-only access, read-write privilege to file
			* Cord keyboard
			** Marco keyboard that allows messages quickly, while using mouse at same time
			* Not really a distributed operating system, but great start because multiple users at different terminals could share same resources

			== Early Internet ==

			== Alto ==

			Team: Tory, Veena, Sameer, Mert, Deep, Nameet, Moe

			* 1973
			* High speed (3 Mbps @ 1km difference)
			* Connects up to 256 machines
			* Protocol similar to cross between UDP/TCP, before TCP invented
			* Allowed sharing printers
			* Also allowed for distributing files across computers (redundancy/reliability)
			* Sort of early cloud
			* Allowed for remote debugging, store error logs
			* Allowed machines to use processing power of others
			* much of the time it would be doing nothing