backup/EWF
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

fixed github wikitext usage

Browse Source
This commit is contained in:
Jocelyn Fiat
2012-05-26 00:08:28 +03:00
parent b37a2bd17f
commit 4324b83cba
1 changed files with 8 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
examples/tutorial/README.wiki
View File

@@ -1,21 +1,24 @@
= Eiffel Web Framework = = Eiffel Web Framework =
== Why would you use the Eiffel Web Framework ? == == Why would you use the Eiffel Web Framework ? ==
To enjoy the advantage of the Eiffel technology (language, DbC, methods, tools) To enjoy the advantage of the Eiffel technology (language, DbC, methods, tools)
To write once and run on any web server, on any platforms thanks to the notion of connector. To write once and run on any web server, on any platforms thanks to the notion of connector.
== What is a connector? == == What is a connector? ==
A connector is the layer between the underlying httpd server, and your application based on EWF. A connector is the layer between the underlying httpd server, and your application based on EWF.
Currently, 3 connectors are available within EWF (but others are available outside). Currently, 3 connectors are available within EWF (but others are available outside).
­ CGI: the common CGI application (apache, iis, ...) *­ CGI: the common CGI application (apache, iis, ...)
- FastCGI: on any server supporting libfcgi handling (apache, iis, ...) * FastCGI: on any server supporting libfcgi handling (apache, iis, ...)
- Nino: using the standalone Eiffel Web Nino server, you can run anywhere easily, and debug simply with EiffelStudio's debugger * Nino: using the standalone Eiffel Web Nino server, you can run anywhere easily, and debug simply with EiffelStudio's debugger
Supporting a new connector is fairly simple, it just has to support the simple EWSGI specification which is really small. Then EWF will bring the power on top of it. Supporting a new connector is fairly simple, it just has to support the simple EWSGI specification which is really small. Then EWF will bring the power on top of it.
So you can build your application and be sure you will be able to run it ... anywhere thanks to the conceіpt of connectors. So you can build your application and be sure you will be able to run it ... anywhere thanks to the conceіpt of connectors.
== EWSGI specification == == EWSGI specification ==
EWF relies on a small core specification, named EWSGI (Eiffel Web Servєr Gateway Interface). EWF relies on a small core specification, named EWSGI (Eiffel Web Servєr Gateway Interface).
It is very limited on purpose to allow building new connector very easily. It is very limited on purpose to allow building new connector very easily.
@@ -23,7 +26,8 @@ For now, you just need to know EWF is compliant with EWSGI specification.
= Tutorial = = Tutorial =
Now let's discover the Eiffel Web Framework with this tutorial. Now let's discover the Eiffel Web Framework with this tutorial:
# [[step_1.wiki|Step #1]]: You will learn first, how to get and install EWF. # [[step_1.wiki|Step #1]]: You will learn first, how to get and install EWF.
# [[step_2.wiki|Step #2]]: build a simple Hello World application # [[step_2.wiki|Step #2]]: build a simple Hello World application
# [[step_3.wiki|Step #3]]: use the parameter to build dynamic service # [[step_3.wiki|Step #3]]: use the parameter to build dynamic service