CSC/ECE 517 Spring 2015 M1502 WSRA - Revision history

Wpgallih: /* Test Cases */

2015-05-05T07:06:52Z

Test Cases

← Older revision		Revision as of 07:06, 5 May 2015
Line 85:		Line 85:
	./mach run tests/html/test-websocket.html		./mach run tests/html/test-websocket.html
	</code>		</code>

			This code will open a websocket, print connected, send a message, then print a received message before closing. As stated before, this is more a test to interface tool, instead of testing the conformance to spec and robustness of the code created.

	==Further Readings==		==Further Readings==

Wpgallih: /* Test Cases */

2015-05-05T07:03:21Z

Test Cases

@@ Line 67: / Line 67: @@
 [websockets]<br>
 skip: false<br>
 </code>

Wpgallih: /* Test Cases */

2015-05-05T06:54:40Z

Test Cases

← Older revision		Revision as of 06:54, 5 May 2015
Line 64:		Line 64:

	First, to include the websocket tests, add the following lines in the tests/wpt/include.ini file:		First, to include the websocket tests, add the following lines in the tests/wpt/include.ini file:
	<code>		<code><br>
	[websockets]		[websockets]<br>
	skip: false		skip: false<br>
	</code>		</code>

Wpgallih: /* Proposed Test Cases */

2015-05-05T06:53:52Z

Proposed Test Cases

← Older revision		Revision as of 06:53, 5 May 2015
Line 59:		Line 59:
	Servo's primary objective was to provide concurrency. This concurrency can be attained by scheduling tasks which can be run in parallel. Threads help execute these tasks in parallel. Thread Pool Pattern helps manage these thread. For example, one thread could be to accept new requests for websockets, as a result of which new thread would be spawned (client side of websocket) for that application.		Servo's primary objective was to provide concurrency. This concurrency can be attained by scheduling tasks which can be run in parallel. Threads help execute these tasks in parallel. Thread Pool Pattern helps manage these thread. For example, one thread could be to accept new requests for websockets, as a result of which new thread would be spawned (client side of websocket) for that application.

	==~~Proposed~~ Test Cases==		==Test Cases==

	The test cases for ~~websocket~~ are already included in ~~servo~~, ~~under~~ the ~~Servo directory~~ tests~~/wpt/web-platform-tests/websockets. To break down~~ how ~~each should~~ be ~~tested, here are the proposed scenarios:~~		The test cases for WebSocket are already implemented and included in Servo. Servo uses a testing system which allows skipping of features not included, or passed. Therefore, when the WebSocket tests are included, it is not only necessary to know how to run them, it is important to be able to use the tools that automatically update the tests passed as well.
	* The send function should send some object, then wait for confirmation of sending.
	* The constructor should make a websocket connection to the ~~URL and either open~~ the ~~connection or close it based on the response coming in.~~
	* The receive function should trigger on receiving an object, then send confirmation.

	~~All of these are tested thoroughly~~ in the ~~directory given at the beginning of this section~~.		First, to include the websocket tests, add the following lines in the tests/wpt/include.ini file:
			<code>
			[websockets]
			skip: false
			</code>

	==Further Readings==		==Further Readings==

Achen4: /* Implementation */

2015-05-04T23:14:26Z

Implementation

← Older revision		Revision as of 23:14, 4 May 2015
Line 36:		Line 36:

	==Implementation==		==Implementation==
	~~'''When the WebSocket connection is established, the user agent must queue a task to run these steps~~:~~'''~~		The full implementation specs are outlined here: https://github.com/servo/servo/wiki/WebSocket-student-project
	*If the WebSocket ~~object's client~~-~~specified protocols was not an empty list, but the subprotocol in use is the null value, then fail the WebSocket connection, set the readyState attribute's value to CLOSING, and abort these steps.~~
	*Change the readyState attribute's value to OPEN.
	*Change the extensions attribute's value to the extensions in use, if is not the null value.
	*Change the protocol attribute's value to the subprotocol in use, if is not the null value.
	*Act as if the user agent had received a set-~~cookie-string consisting of the cookies set during the server's opening handshake, for the URL url given to the WebSocket() constructor.~~
	*Fire a simple event named open at the WebSocket object.

	~~'''When a WebSocket message~~ has ~~been received with type type~~ and ~~data data,~~ the ~~user agent must queue a task~~ to ~~follow these steps:'''~~		In general the websocket has 3 functions:
	*If the ~~readyState attribute's value~~ is ~~not OPEN~~, ~~then abort these steps~~.		*Open() - Initiates and connects the websocket to the server. Once the connection is open, hands receives.
	*~~Let event be a newly created trusted event that uses~~ the ~~MessageEvent interface, with~~ the ~~event type message, which does not bubble, is not cancelable, and~~ has ~~no default action.~~		*Send() - Sends application data to the server
	*~~Initialise event's origin attribute to~~ the ~~Unicode serialisation~~ of the ~~origin~~ of the ~~URL that was passed~~ to the ~~WebSocket object's constructor.~~		*Close() - Closes the websocket connection
	*~~If type indicates that~~ the ~~data is Text, then initialise event's data attribute~~ to ~~data.~~
	*~~If type indicates that~~ the ~~data is Binary, and binaryType is set~~ to ~~"blob", then initialise event's data attribute to a new Blob object that represents data as its raw data.~~		In addition the websocket has the following attributes:
	*~~If type indicates that~~ the ~~data is Binary,~~ and ~~binaryType is set to "arraybuffer", then initialise event's data attribute to a new ArrayBuffer object whose contents~~ are ~~data.~~		*readyState - indicates the current state of the websocket. The websocket can be in one of the five states below:
	*~~Dispatch event at~~ the ~~WebSocket object.~~		**Connecting - an initial connection handshake has been started but the server has not responded to the handshake yet
			**Open - the connection has been established (server has responded to the initial connection handshake)
			**Closing - an initial close connection handshake has been started but the server has not responded to the handshake yet
			**Closed - the connection has been closed (server has acknowledged the closing handshake and responded)
			*Extensions - Extensions are being used by the websocket (see full specs link above)
			*Protocol - Protocols being used by the websocket (see full specs link above)
			*bufferedAmount - returns how many bytes of application data has been buffered in the websocket thus far (unsent data)

	==Design Patterns==		==Design Patterns==

Wpgallih: /* Further Readings */

2015-04-02T01:56:30Z

Wpgallih: /* Further Readings */

2015-04-02T01:56:02Z

Wpgallih: /* Further Readings */

2015-04-02T01:55:26Z

Wpgallih: /* Proposed Test Cases */

2015-04-02T01:53:04Z

Proposed Test Cases

← Older revision		Revision as of 01:53, 2 April 2015
Line 60:		Line 60:

	==Proposed Test Cases==		==Proposed Test Cases==

			The test cases for websocket are already included in servo, under the Servo directory tests/wpt/web-platform-tests/websockets. To break down how each should be tested, here are the proposed scenarios:
			* The send function should send some object, then wait for confirmation of sending.
			* The constructor should make a websocket connection to the URL and either open the connection or close it based on the response coming in.
			* The receive function should trigger on receiving an object, then send confirmation.

			All of these are tested thoroughly in the directory given at the beginning of this section.

	==Further Readings==		==Further Readings==
	==References==		==References==
	<references/>		<references/>

Wpgallih at 01:43, 2 April 2015

2015-04-02T01:43:37Z

← Older revision		Revision as of 01:43, 2 April 2015
Line 53:		Line 53:
	*Dispatch event at the WebSocket object.		*Dispatch event at the WebSocket object.

	~~==Architecture==~~
	~~==Component Design==~~
	~~==Data Design==~~
	==Design Patterns==		==Design Patterns==
	<b>[http://en.wikipedia.org/wiki/Factory_%28object-oriented_programming%29 Factory Pattern]</b><br>		<b>[http://en.wikipedia.org/wiki/Factory_%28object-oriented_programming%29 Factory Pattern]</b><br>

← Older revision		Revision as of 01:56, 2 April 2015
Line 69:		Line 69:

	==Further Readings==		==Further Readings==
	<b>[https://html.spec.whatwg.org/multipage/comms.html#network HTML Spec for WebSockets]</b>		<b>[https://html.spec.whatwg.org/multipage/comms.html#network HTML Spec for WebSockets]</b><br>
	<b>[https://github.com/servo/servo/wiki/WebSocket-student-project Mozilla Websocket Project Page]</b>		<b>[https://github.com/servo/servo/wiki/WebSocket-student-project Mozilla Websocket Project Page]</b><br>
	<b>[https://github.com/servo/servo Servo github]</b>		<b>[https://github.com/servo/servo Servo github]</b><br>
	<b>[http://cyderize.github.io/rust-websocket/ Rust Websocket]</b>		<b>[http://cyderize.github.io/rust-websocket/ Rust Websocket]</b><br>

	==References==		==References==
	<references/>		<references/>

← Older revision		Revision as of 01:56, 2 April 2015
Line 69:		Line 69:

	==Further Readings==		==Further Readings==
	[https://html.spec.whatwg.org/multipage/comms.html#network HTML Spec for WebSockets]		<b>[https://html.spec.whatwg.org/multipage/comms.html#network HTML Spec for WebSockets]</b>
	[https://github.com/servo/servo/wiki/WebSocket-student-project Mozilla Websocket Project Page]		<b>[https://github.com/servo/servo/wiki/WebSocket-student-project Mozilla Websocket Project Page]</b>
	[https://github.com/servo/servo Servo github]		<b>[https://github.com/servo/servo Servo github]</b>
	[http://cyderize.github.io/rust-websocket/ Rust Websocket]		<b>[http://cyderize.github.io/rust-websocket/ Rust Websocket]</b>

	==References==		==References==
	<references/>		<references/>

← Older revision		Revision as of 01:55, 2 April 2015
Line 69:		Line 69:

	==Further Readings==		==Further Readings==
			[https://html.spec.whatwg.org/multipage/comms.html#network HTML Spec for WebSockets]
			[https://github.com/servo/servo/wiki/WebSocket-student-project Mozilla Websocket Project Page]
			[https://github.com/servo/servo Servo github]
			[http://cyderize.github.io/rust-websocket/ Rust Websocket]

	==References==		==References==
	<references/>		<references/>