Difference between revisions of "HOW EXACTLY TO Code A Ruby on Rails Web Application"
m |
m |
||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | Ruby on Rails is really a web application framework.<br /><br />Rails | + | Ruby on Rails is really a web application framework.<br /><br />Rails may be the framework, Ruby is the language.<br /><br />Designed by David Heinemeier Hansson in 2005, it's become renowned in the Internet startup world because of its adoption by a number of the leading "startups" of our time, including Stripe, Uber and Groupon.<br /><br />If you want to learn to program in Ruby on Rails, this tutorial should offer you an overview of what to do. I won't go into specifics because I simply want to give you an idea as to the structure of an application. If you follow what I propose, you need to more grasp how these applications work.<br /><br />Web Applications<br /><br />All software applications work in the same way -<br /><br />Data is inputted<br />Data is processed<br />Data is outputted<br />The way the data is inputted and processed is dependent on the platform the application runs on. How it is outputted depends on your application.<br />The difference with web applications is that their logic runs on a server, with the data IO being passed through the Internet (specifically, the HTTP protocol).<br /><br />The complication of web apps is that you require the ability to accept inbound data, and return responses. That is handled by a web server program (NGinx or Apache). I'll explain this in a minute.<br /><br />Software Stack<br /><br />When you create a piece of software, you have to consider the "stack" on which it runs.<br /><br />The "stack" is all of the software required to run your application. In the world of desktop games, for example, the "stack" may include famous brands DirectX or perhaps a particular graphics driver.<br /><br />The primary hold-back for would-be web application developers is understanding how the "web" software stack works. Web works much like native applications, except for one distinct difference - stateless.<br /><br />The "Internet" operates beneath the HTTP protocol. By nature, this is referred to as a "stateless" protocol - each request you send is known as independent to the last. Unlike stateful protocols (which retain state), stateless protocols need to rebuild the application's state each and every time.<br /><br /> [https://flipboard.com/@langstonowen6 website] means nothing to most people, the point is that if you're going to develop a web based application, you should employ a framework or technology set which makes the stateless nature of HTTP as integrated as possible. Most pertinently, you need an authentication system which rebuilds the user's session on every request (I'll explain this in another). |
Latest revision as of 16:45, 28 April 2021
Ruby on Rails is really a web application framework.
Rails may be the framework, Ruby is the language.
Designed by David Heinemeier Hansson in 2005, it's become renowned in the Internet startup world because of its adoption by a number of the leading "startups" of our time, including Stripe, Uber and Groupon.
If you want to learn to program in Ruby on Rails, this tutorial should offer you an overview of what to do. I won't go into specifics because I simply want to give you an idea as to the structure of an application. If you follow what I propose, you need to more grasp how these applications work.
Web Applications
All software applications work in the same way -
Data is inputted
Data is processed
Data is outputted
The way the data is inputted and processed is dependent on the platform the application runs on. How it is outputted depends on your application.
The difference with web applications is that their logic runs on a server, with the data IO being passed through the Internet (specifically, the HTTP protocol).
The complication of web apps is that you require the ability to accept inbound data, and return responses. That is handled by a web server program (NGinx or Apache). I'll explain this in a minute.
Software Stack
When you create a piece of software, you have to consider the "stack" on which it runs.
The "stack" is all of the software required to run your application. In the world of desktop games, for example, the "stack" may include famous brands DirectX or perhaps a particular graphics driver.
The primary hold-back for would-be web application developers is understanding how the "web" software stack works. Web works much like native applications, except for one distinct difference - stateless.
The "Internet" operates beneath the HTTP protocol. By nature, this is referred to as a "stateless" protocol - each request you send is known as independent to the last. Unlike stateful protocols (which retain state), stateless protocols need to rebuild the application's state each and every time.
website means nothing to most people, the point is that if you're going to develop a web based application, you should employ a framework or technology set which makes the stateless nature of HTTP as integrated as possible. Most pertinently, you need an authentication system which rebuilds the user's session on every request (I'll explain this in another).
