umgeher/cowboy
0
Fork 0
mirror of https://github.com/ninenines/cowboy.git synced 2025-07-14 20:30:23 +00:00
Code Issues Wiki Activity

Minor corrections of the guide

Browse source
This commit is contained in:
Matthias Endler 2013-06-27 01:01:01 +02:00
parent 61ca86b054
commit f664329b0b
3 changed files with 4 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

4
guide/erlang_web.md
View file

@ -43,7 +43,7 @@ designed to work in a distributed setting, so it is a
perfect match. perfect match.
Or is it? Surely you can find solutions to handle that many Or is it? Surely you can find solutions to handle that many
concurrent connections with my favorite language... But all concurrent connections with your favorite language... But all
these solutions will break down in the next few years. Why? these solutions will break down in the next few years. Why?
Firstly because servers don't get any more powerful, they Firstly because servers don't get any more powerful, they
instead get a lot more cores and memory. This is only useful instead get a lot more cores and memory. This is only useful
@ -90,7 +90,7 @@ The Web is asynchronous
Long ago, the Web was synchronous because HTTP was synchronous. Long ago, the Web was synchronous because HTTP was synchronous.
You fired a request, and then waited for a response. Not anymore. You fired a request, and then waited for a response. Not anymore.
It all started when XmlHttpRequest started being used. It allowed It all began when XmlHttpRequest started being used. It allowed
the client to perform asynchronous calls to the server. the client to perform asynchronous calls to the server.
Then Websocket appeared and allowed both the server and the client Then Websocket appeared and allowed both the server and the client

2
guide/getting_started.md
View file

@ -50,7 +50,7 @@ we will just use the plain HTTP handler, which has three callback
functions: init/3, handle/2 and terminate/3. You can find more information functions: init/3, handle/2 and terminate/3. You can find more information
about the arguments and possible return values of these callbacks in the about the arguments and possible return values of these callbacks in the
[cowboy_http_handler function reference](http://ninenines.eu/docs/en/cowboy/HEAD/manual/cowboy_http_handler). [cowboy_http_handler function reference](http://ninenines.eu/docs/en/cowboy/HEAD/manual/cowboy_http_handler).
Following is an example of a simple HTTP handler module. Here is an example of a simple HTTP handler module.
``` erlang ``` erlang
-module(my_handler). -module(my_handler).

2
guide/modern_web.md
View file

@ -66,7 +66,7 @@ of concerns between the client and the server. They communicate
by referencing resources. Resources can be identified, but by referencing resources. Resources can be identified, but
also manipulated. A resource representation has a media type also manipulated. A resource representation has a media type
and information about whether it can be cached and how. Hypermedia and information about whether it can be cached and how. Hypermedia
determines how resources are related and they can be used. determines how resources are related and how they can be used.
REST is also stateless. All requests contain the complete REST is also stateless. All requests contain the complete
information necessary to perform the action. information necessary to perform the action.