CSC/ECE 517 Spring 2015/ch1a 12 LS - Revision history

Hwang40: /* Template streaming */

2015-02-16T04:08:01Z

Template streaming

← Older revision		Revision as of 04:08, 16 February 2015
Line 9:		Line 9:

	='''Examples'''=		='''Examples'''=
	==Template ~~streaming~~==		==Template Streaming==
	Some basic knowledge about how web pages are rendered can be found [http://friendlybit.com/css/rendering-a-web-page-step-by-step/ here] and also [http://www.pathinteractive.com/blog/2014/07/rendering-a-webpage-with-google-webmaster-tools/ here]. <br><br>		Some basic knowledge about how web pages are rendered can be found [http://friendlybit.com/css/rendering-a-web-page-step-by-step/ here] and also [http://www.pathinteractive.com/blog/2014/07/rendering-a-webpage-with-google-webmaster-tools/ here]. <br><br>
	Since Rail 3.1, [http://api.rubyonrails.org/classes/ActionController/Streaming.html ''::Streaming''] module has been added to ActionController. For example, the loading progress in a traditional Rails client-side may look like this<ref>Template Streaming, George Ogata https://github.com/oggy/template_streaming</ref>:		Since Rail 3.1, [http://api.rubyonrails.org/classes/ActionController/Streaming.html ''::Streaming''] module has been added to ActionController. For example, the loading progress in a traditional Rails client-side may look like this<ref>Template Streaming, George Ogata https://github.com/oggy/template_streaming</ref>:

Hwang40: /* Live Streaming */

2015-02-16T04:07:34Z

Live Streaming

← Older revision		Revision as of 04:07, 16 February 2015
Line 133:		Line 133:
	[[File:nostreaming.gif]]		[[File:nostreaming.gif]]

	===Live ~~Streaming~~===		===Live Aproach===
	In order to enable live streaming, we need to include a module named ''ActionController::Live''. When this module is mixed into the controller, all actions within that controller will be able to stream data to the client in real time, like the following code:		In order to enable live streaming, we need to include a module named ''ActionController::Live''. When this module is mixed into the controller, all actions within that controller will be able to stream data to the client in real time, like the following code:
	<pre>		<pre>

Ylu31: /* Conclusion */

2015-02-16T04:00:47Z

Conclusion

← Older revision		Revision as of 04:00, 16 February 2015
Line 251:		Line 251:

	='''Conclusion'''=		='''Conclusion'''=
			The supporting for live streaming has deep impact on Rails. It not only makes Rails more competitive with Node.js, but also opens a gate for Rails to embrace lots of new areas and applications that it does not fits well before. The main advantage of Rails can be summarized as follows:<br>

	1.Send partial responses to the client immediately.		1.Send partial responses to the client immediately.
	<br>		<br>
	2.Using Server-sent events, the ability to create chat clients, push notifications, and real-time feeds are available within Rails itself		2.Using Server-sent events, the ability to create chat clients, push notifications, and real-time feeds are available within Rails itself.
	<br>		<br>
	3.Continuously inform the user about the progress.		3.Continuously inform the user about the progress.

Ylu31: /* Template streaming */

2015-02-16T03:46:40Z

Template streaming

← Older revision		Revision as of 03:46, 16 February 2015
Line 10:		Line 10:
	='''Examples'''=		='''Examples'''=
	==Template streaming==		==Template streaming==
	Some basic knowledge about how web pages are rendered can be found [http://friendlybit.com/css/rendering-a-web-page-step-by-step/ here] and [http://www.pathinteractive.com/blog/2014/07/rendering-a-webpage-with-google-webmaster-tools/ here]. <br><br>		Some basic knowledge about how web pages are rendered can be found [http://friendlybit.com/css/rendering-a-web-page-step-by-step/ here] and also [http://www.pathinteractive.com/blog/2014/07/rendering-a-webpage-with-google-webmaster-tools/ here]. <br><br>
	Since Rail 3.1, [http://api.rubyonrails.org/classes/ActionController/Streaming.html ''::Streaming''] module has been added to ActionController. For example, the loading progress in a traditional Rails client-side may look like this<ref>Template Streaming, George Ogata https://github.com/oggy/template_streaming</ref>:		Since Rail 3.1, [http://api.rubyonrails.org/classes/ActionController/Streaming.html ''::Streaming''] module has been added to ActionController. For example, the loading progress in a traditional Rails client-side may look like this<ref>Template Streaming, George Ogata https://github.com/oggy/template_streaming</ref>:
	<div class="center" style="width: auto; margin-left: auto; margin-right: auto;">		<div class="center" style="width: auto; margin-left: auto; margin-right: auto;">

Hwang40 at 03:38, 16 February 2015

2015-02-16T03:38:06Z

← Older revision		Revision as of 03:38, 16 February 2015
Line 250:		Line 250:
	<br>		<br>

	='''~~Benefit of live streaming~~'''=		='''Conclusion'''=
	1.Send partial responses to the client immediately.		1.Send partial responses to the client immediately.
	<br>		<br>

Hwang40 at 03:37, 16 February 2015

2015-02-16T03:37:40Z

← Older revision		Revision as of 03:37, 16 February 2015
Line 8:		Line 8:
	__TOC__		__TOC__

	='''~~Details~~'''=		='''Examples'''=
	==Template streaming==		==Template streaming==
	Some basic knowledge about how web pages are rendered can be found [http://friendlybit.com/css/rendering-a-web-page-step-by-step/ here] and [http://www.pathinteractive.com/blog/2014/07/rendering-a-webpage-with-google-webmaster-tools/ here]. <br><br>		Some basic knowledge about how web pages are rendered can be found [http://friendlybit.com/css/rendering-a-web-page-step-by-step/ here] and [http://www.pathinteractive.com/blog/2014/07/rendering-a-webpage-with-google-webmaster-tools/ here]. <br><br>
Line 250:		Line 250:
	<br>		<br>

	==Benefit of live streaming==		='''Benefit of live streaming'''=
	1.Send partial responses to the client immediately.		1.Send partial responses to the client immediately.
	<br>		<br>

Ylu31: /* Template streaming */

2015-02-16T03:30:27Z

Template streaming

← Older revision		Revision as of 03:30, 16 February 2015
Line 18:		Line 18:
	<br>		<br>
	<br>		<br>
	The module ''::Streaming'' inverts the regular Rails process of rendering the layout and template. Using ''::Streaming'', Rails will render template first and then layout. It will first run method yield and load up the template, and then renders the assets and layouts. In this way, the progress with streaming looks like this:		The module ''::Streaming'' inverts the regular Rails process of rendering the layout and template. Using ''::Streaming'', Rails will render template first and then layout. It will first run method ''yield'' and load up the template, and then renders the assets and layouts. In this way, the progress with streaming looks like this:
	<div class="center" style="width: auto; margin-left: auto; margin-right: auto;">		<div class="center" style="width: auto; margin-left: auto; margin-right: auto;">
	[[File:fast-profile.png]]</div>		[[File:fast-profile.png]]</div>
Line 25:		Line 25:

	===When to use streaming===		===When to use streaming===
	For actions like new or edit, it may not be that necessary to use streaming. But for expensive actions like database query and generation of large amount of data, streaming can be extremely important and effective. Take the following action as an example:		For actions like ''new'' or ''edit'', it may not be that necessary to use streaming. But for expensive actions like database query and generation of large amount of data, streaming can be extremely important and effective. Take the following action as an example:
	<pre>		<pre>
	def storyboard		def storyboard

Ylu31: /* Template streaming */

2015-02-16T03:26:01Z

Template streaming

← Older revision		Revision as of 03:26, 16 February 2015
Line 10:		Line 10:
	='''Details'''=		='''Details'''=
	==Template streaming==		==Template streaming==
			Some basic knowledge about how web pages are rendered can be found [http://friendlybit.com/css/rendering-a-web-page-step-by-step/ here] and [http://www.pathinteractive.com/blog/2014/07/rendering-a-webpage-with-google-webmaster-tools/ here]. <br><br>
	Since Rail 3.1, [http://api.rubyonrails.org/classes/ActionController/Streaming.html ''::Streaming''] module has been added to ActionController. For example, the loading progress in a traditional Rails client-side may look like this<ref>Template Streaming, George Ogata https://github.com/oggy/template_streaming</ref>:		Since Rail 3.1, [http://api.rubyonrails.org/classes/ActionController/Streaming.html ''::Streaming''] module has been added to ActionController. For example, the loading progress in a traditional Rails client-side may look like this<ref>Template Streaming, George Ogata https://github.com/oggy/template_streaming</ref>:
	<div class="center" style="width: auto; margin-left: auto; margin-right: auto;">		<div class="center" style="width: auto; margin-left: auto; margin-right: auto;">

Hwang40: /* Troubleshooting */

2015-02-16T03:22:06Z

Troubleshooting

← Older revision		Revision as of 03:22, 16 February 2015
Line 303:		Line 303:
	</pre>		</pre>
	<br>		<br>
	To solve this problem, we need to install [https://www.openssl.org/ openssl] for windows. And then run the following command<ref>https://github.com/hicknhack-software/rails-disco/wiki/Installing-puma-on-windows</ref>:		To solve this problem, we need to install [https://www.openssl.org/ openssl] for windows. And then run the following command<ref>Installing puma on windows, Robert Kranz https://github.com/hicknhack-software/rails-disco/wiki/Installing-puma-on-windows</ref>:
	<pre>		<pre>
	gem install puma -- --with-opt-dir=c:\openssl		gem install puma -- --with-opt-dir=c:\openssl

Hwang40: /* Server-Sent Event */

2015-02-16T03:20:49Z

Server-Sent Event

← Older revision		Revision as of 03:20, 16 February 2015
Line 155:		Line 155:

	==Server-Sent Event==		==Server-Sent Event==
	[https://en.wikipedia.org/wiki/Server-sent_events Server-sent event (SSE)] is a technology where browser can automatically receive update data from a server via [https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol HTTP] connection. Whenever server sends data, the SSE method in the browser will trigger an event.The SSE EventSource API is standardized as part of [https://en.wikipedia.org/wiki/HTML5 HTML5] by the [https://en.wikipedia.org/wiki/World_Wide_Web_Consortium W3C]. It can be used together with the Live API to achieve full-duplex communication.<ref>https://en.wikipedia.org/wiki/Server-sent_events</ref>		[https://en.wikipedia.org/wiki/Server-sent_events Server-sent event (SSE)] is a technology where browser can automatically receive update data from a server via [https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol HTTP] connection. Whenever server sends data, the SSE method in the browser will trigger an event.The SSE EventSource API is standardized as part of [https://en.wikipedia.org/wiki/HTML5 HTML5] by the [https://en.wikipedia.org/wiki/World_Wide_Web_Consortium W3C]. It can be used together with the Live API to achieve full-duplex communication.<ref>Server-sent events https://en.wikipedia.org/wiki/Server-sent_events</ref>
	<br>		<br>
	A simple SSE looks like the following :		A simple SSE looks like the following :