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

merged wiki page changes

Browse Source
This commit is contained in:
Jocelyn Fiat
2013-11-18 17:34:03 +00:00
parent a0665313ed 373e13208f
commit d15da0ffd4
15 changed files with 146 additions and 54 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
doc/wiki/Community-collaboration.md
View File

@@ -1,13 +1,13 @@
This project is a community project This project is a community project
## Mailing list ## ## Mailing list ##
- Google group: http://groups.google.com/group/eiffel-web-framework - Google group: [http://groups.google.com/group/eiffel-web-framework](http://groups.google.com/group/eiffel-web-framework)
## Materials ## ## Materials ##
- wiki: github wiki at https://github.com/Eiffel-World/Eiffel-Web-Framework/wiki - wiki: github wiki at [https://github.com/Eiffel-World/Eiffel-Web-Framework/wiki](https://github.com/Eiffel-World/Eiffel-Web-Framework/wiki)
- Shared documents: on google docs at http://goo.gl/M8WLP - Shared documents: on google docs at [http://goo.gl/M8WLP](http://goo.gl/M8WLP)
- source code: git repository at https://github.com/Eiffel-World/Eiffel-Web-Framework - source code: git repository at [https://github.com/Eiffel-World/Eiffel-Web-Framework](https://github.com/Eiffel-World/Eiffel-Web-Framework)
- Proposal from Paul Cohen for a EWSGI spec at http://eiffel.seibostudios.se/wiki/EWSGI - Proposal from Paul Cohen for a EWSGI spec at [http://eiffel.seibostudios.se/wiki/EWSGI](http://eiffel.seibostudios.se/wiki/EWSGI)
## Main contributors ## ## Main contributors ##
- **jfiat**: Jocelyn Fiat (Eiffel Software) - **jfiat**: Jocelyn Fiat (Eiffel Software)

48
doc/wiki/Connectors.md Normal file
View File

@@ -0,0 +1,48 @@
The main goal of the connectors is to let you choose a target at compile time.
This allows you to concentrate on your business during development time and then decide which target you choose at deployment time.
The current connectors are:
* Nino
* FastCGI
* CGI
* OpenShift
The most widely used workflow is to use Nino on your development machine and FastCGI on your production server.
Nino being a web server written entirely in Eiffel, you can inspect your HTTP requests and respones in EiffelStudio which is great during development.
On the other hand, FastCGI is great at handling concurrent requests and coupled with Apache (or another web production server), you don't even need to worry about the lifecyle of your application (creation and destruction) as Apache will do it for you!
Let's now dig into each of the connecters.
# Nino
Nino is a web server entirely written in Eiffel.
The goal of Nino is to provide a simple web server for development (like Java, Python and Ruby provide).
Nino is currently maintained by Javier Velilla and the repository can be found here: https://github.com/jvelilla/EiffelWebNino
# FastCGI
FastCGI is a protocol for interfacing an application server with a web server.
It is an improvement over CGI as FastCGI supports long running processes, i.e. processes than can handle multipe requests during their lifecyle. CGI, on the other hand, launches a new process for every new request which is quite time consuming.
FastCGI is implemented by every major web servers: Apache, IIS, Nginx, ...
We recommend to use FastCGI instead of CGI as it is way more faster.
You can read more about FastCGI here: http://www.fastcgi.com/
# CGI
CGI predates FastCGI and is also a protocol for interfacing an application server with a web server.
His main drawback (and the reason why FastCGI was created) is that it launches a new process for every new request, which is quite time consuming.
We recommend to use FastCGI instead of CGI as it is way more faster.
# OpenShift
OpenShift is a cloud computing platform as a service product from Red Hat.
It basically let's you run your application in the cloud.
More informations are available here: https://www.openshift.com
# Writing your own
It's fairly easy to write your own connector. Just inherit from these classes:
* WGI_CONNECTOR
* WGI_ERROR_STREAM
* WGI_INPUT_STREAM
* WGI_OUTPUT_STREAM
* WSF_SERVICE_LAUNCHER

4
doc/wiki/EWSGI-specification.md
View File

@@ -4,7 +4,7 @@
## Preface ## Preface
This specification is a proposition based on recent discussion on the mailing list. This specification is a proposition based on recent discussion on the mailing list.
This is work in progress, so far nothing had been decided. This is work in progress, so far nothing had been decided.
You can find another proposal at http://eiffel.seibostudios.se/wiki/EWSGI , it has common background and goal, however still differ on specific parts. You can find another proposal at [http://eiffel.seibostudios.se/wiki/EWSGI](http://eiffel.seibostudios.se/wiki/EWSGI) , it has common background and goal, however still differ on specific parts.
The main goal for now is to unified those 2 specifications. The main goal for now is to unified those 2 specifications.
--- ---
@@ -12,7 +12,7 @@ Note the following is work in progress, and reflect a specification proposal, ra
2011-08-01 2011-08-01
--- ---
For now, the specification from EWF is done in Eiffel interface For now, the specification from EWF is done in Eiffel interface
please see: https://github.com/Eiffel-World/Eiffel-Web-Framework/tree/master/library/server/ewsgi/specification please see: [https://github.com/Eiffel-World/Eiffel-Web-Framework/tree/master/library/server/ewsgi/specification](https://github.com/Eiffel-World/Eiffel-Web-Framework/tree/master/library/server/ewsgi/specification)
WGI_APPLICATION WGI_APPLICATION

4
doc/wiki/EWSGI.md
View File

@@ -1,5 +1,5 @@
- See proposed specifications: [[EWSGI specification| EWSGI-specification]] - See proposed specifications: [EWSGI specification](./EWSGI-specification)
- See [[Open questions| EWSGI-open-questions]] - See [Open questions](./EWSGI-Open-Questions)
- And below the various proposals and associated decision - And below the various proposals and associated decision
---- ----

27
doc/wiki/Filter.md Normal file
View File

@@ -0,0 +1,27 @@
# Introduction
The basic idea of a filter is to pre-process incoming data and post-process outgoing data.
Filters are part of a filter chain, thus following the [chain of responsability design pattern](http://en.wikipedia.org/wiki/Chain-of-responsibility_pattern).
Each filter decides to call the next filter or not.
# Levels
In EWF, there are two levels of filters.
## WSF_FILTER
Typical examples of such filters are: logging, compression, routing (WSF_ROUTING_FILTER), ...
## WSF_FILTER_HANDLER
Handler that can also play the role of a filter.
Typical examples of such filters are: authentication, ...
# References
Filters (also called middelwares) in other environments:
* in Python: http://www.wsgi.org/en/latest/libraries.html
* in Node.js: http://expressjs.com/guide.html#middleware
* in Apache: http://httpd.apache.org/docs/2.2/en/filter.html

22
doc/wiki/Home.md
View File

@@ -1,26 +1,26 @@
# Eiffel-Web-Framework # # Eiffel-Web-Framework #
## Location ## ## Location ##
The official documentation/wiki is located at https://github.com/EiffelWebFramework/EWF/wiki , if you are visiting a "clone/fork", please always check the [[official wiki|https://github.com/EiffelWebFramework/EWF/wiki]]. The official documentation/wiki is located at [https://github.com/EiffelWebFramework/EWF/wiki](https://github.com/EiffelWebFramework/EWF/wiki) , if you are visiting a "clone/fork", please always check the [official wiki](https://github.com/EiffelWebFramework/EWF/wiki).
## Organization ## ## Organization ##
- Mailing list: please visit and subscribe to the mailing list page [[http://groups.google.com/group/eiffel-web-framework]] ![logo](http://groups.google.com/intl/en/images/logos/groups_logo_sm.gif) - Mailing list: please visit and subscribe to the mailing list page [http://groups.google.com/group/eiffel-web-framework](http://groups.google.com/group/eiffel-web-framework) ![logo](http://groups.google.com/intl/en/images/logos/groups_logo_sm.gif)
- Most of the topics are discussed on the mailing list (google group). - Most of the topics are discussed on the mailing list (google group).
- For time to time we have [[web meetings|meetings]], and less frequently [[physical meetings|meetings]] that occurs usually during other Eiffel related events. - For time to time we have [web meetings](./wiki/Meetings), and less frequently [physical meetings](./wiki/Meetings) that occurs usually during other Eiffel related events.
## Documentation ## ## Documentation ##
- to redo - to redo
## Contributions ## ## Contributions ##
- You want to contribute or follow the progress/discussion, see the [[collaboration page| Community-collaboration]] - You want to contribute or follow the progress/discussion, see the [collaboration page](./wiki/Community-collaboration)
- Potential tasks/projects on EWF: [[Projects page| Projects]] - Potential tasks/projects on EWF: [Projects page](./wiki/Projects)
## See also ## ## See also ##
- [[list of tasks, and a potential roadmap| Tasks-Roadmap]] - [list of tasks, and a potential roadmap](./wiki/Tasks-Roadmap)
- [[General source structure of this project| Source-structure]] - [General source structure of this project](./wiki/Source-structure)
- EWSGI: [[Eiffel Web Server Gateway Interface| EWSGI]] - EWSGI: [Eiffel Web Server Gateway Interface](./wiki/EWSGI)
- [[Overview of the server side architecture| Spec-Server-Architecture]] - [Overview of the server side architecture](./wiki/Spec-Server-Architecture)
- This project is also a collection of [[Libraries]] related to the Web - This project is also a collection of [Libraries](./wiki/Libraries) related to the Web
## Note ## ## Note ##
- This wiki needs to be updated, in the meantime, please have a look at the presentation: https://docs.google.com/presentation/pub?id=1GPFv6aHhTjFSLMnlAt-J4WeIHSGfHdB42dQxmOVOH8s&start=false&loop=false&delayms=3000 - This wiki needs to be updated, in the meantime, please have a look at the presentation: [https://docs.google.com/presentation/pub?id=1GPFv6aHhTjFSLMnlAt-J4WeIHSGfHdB42dQxmOVOH8s&start=false&loop=false&delayms=3000](https://docs.google.com/presentation/pub?id=1GPFv6aHhTjFSLMnlAt-J4WeIHSGfHdB42dQxmOVOH8s&start=false&loop=false&delayms=3000)

2
doc/wiki/Meetings.md
View File

@@ -1,4 +1,4 @@
# Previous and future meetings # Previous and future meetings
* [[Web-meeting: 2012-09-18|Web-meeting-2012-09-18]] * [Web-meeting: 2012-09-18](./Web-meeting-2012-09-18)
* For previous meetings, check the ["meeting" topics](https://groups.google.com/forum/?fromgroups=#!tags/eiffel-web-framework/meeting) on the [forum](http://groups.google.com/group/eiffel-web-framework) * For previous meetings, check the ["meeting" topics](https://groups.google.com/forum/?fromgroups=#!tags/eiffel-web-framework/meeting) on the [forum](http://groups.google.com/group/eiffel-web-framework)

4
doc/wiki/Projects-new-suggestions.md
View File

@@ -1,5 +1,5 @@
Use this to suggest new projects, or request features. Use this to suggest new projects, or request features.
The content of this page will be moved to the main [[Projects]] page for time to time. The content of this page will be moved to the main [Projects](./Projects) page for time to time.
For any entry, please use this template For any entry, please use this template
---- ----
@@ -15,6 +15,6 @@ For any entry, please use this template
## Add support for Swagger ## Add support for Swagger
* _Suggested by **Olivier**_ * _Suggested by **Olivier**_
* _Description_: Build a Swagger Eiffel implementation * _Description_: Build a Swagger Eiffel implementation
* _References_: http://swagger.wordnik.com/ * _References_: [http://swagger.wordnik.com/](http://swagger.wordnik.com/)
---- ----

40
doc/wiki/Projects.md
View File

@@ -6,13 +6,13 @@ If you are a student, don't hesitate to pick one, or even suggest a new project,
## Evaluate EWF according to the following constraints ... ## Evaluate EWF according to the following constraints ...
* _Suggested by **Javier**_ * _Suggested by **Javier**_
* _Description_: According to http://www.amundsen.com/blog/archives/1130 , evaluate the current design of EWF to see if this match the different points. An other option would be to take the following REST implementation toolkit as a guide to evaluate EWF http://code.google.com/p/implementing-rest/wiki/RESTImplementationToolkit. * _Description_: According to [http://www.amundsen.com/blog/archives/1130](http://www.amundsen.com/blog/archives/1130) , evaluate the current design of EWF to see if this match the different points. An other option would be to take the following REST implementation toolkit as a guide to evaluate EWF [http://code.google.com/p/implementing-rest/wiki/RESTImplementationToolkit](http://code.google.com/p/implementing-rest/wiki/RESTImplementationToolkit).
## Road to Hypermedia API ## Road to Hypermedia API
* _Suggested by **Javier**_ * _Suggested by **Javier**_
* _Supervisor_: * _Supervisor_:
* _Suitability_: * _Suitability_:
* _Description_: describe differents types of Web API, and how you can build them using EWF. Describing Pros and Cons. This should be on http://martinfowler.com/articles/richardsonMaturityModel.html * _Description_: describe differents types of Web API, and how you can build them using EWF. Describing Pros and Cons. This should be on [http://martinfowler.com/articles/richardsonMaturityModel.html](http://martinfowler.com/articles/richardsonMaturityModel.html)
## Build a video to demonstrate how an Hypermedia API works, and how to build it using EWF ## Build a video to demonstrate how an Hypermedia API works, and how to build it using EWF
* _Suggested by **Javier**_ * _Suggested by **Javier**_
@@ -55,8 +55,8 @@ If you are a student, don't hesitate to pick one, or even suggest a new project,
* _Supervisor_: * _Supervisor_:
* _Suitability_: TODO * _Suitability_: TODO
* _Description_: EWF is relying on the notion of "connector" to achieve portability on various platform and underlying httpd server, currently EWF support any CGI or libFCGI system (i.e apache, IIS, ...), and provide a standalone version thanks to Eiffel Web Nino. The goal now, would be to support specific connector for: * _Description_: EWF is relying on the notion of "connector" to achieve portability on various platform and underlying httpd server, currently EWF support any CGI or libFCGI system (i.e apache, IIS, ...), and provide a standalone version thanks to Eiffel Web Nino. The goal now, would be to support specific connector for:
** LightHTTP (http://www.lighttpd.net/) ** LightHTTP ([http://www.lighttpd.net/](http://www.lighttpd.net/))
** nginx (http://nginx.org/en/) ** nginx ([http://nginx.org/en/](http://nginx.org/en/))
## Concurrenty and EWF ## Concurrenty and EWF
* _Suggested by **Jocelyn**_ * _Suggested by **Jocelyn**_
@@ -75,7 +75,7 @@ If you are a student, don't hesitate to pick one, or even suggest a new project,
* _Supervisor_: * _Supervisor_:
* _Suitability_: TODO * _Suitability_: TODO
* _Description_: Provide an implementation of websocket with EWF and eventually Eiffel Web Nino, then demonstrate it on a simple example. WebSocket is a web technology providing for bi-directional, full-duplex communications channels over a single TCP connection. * _Description_: Provide an implementation of websocket with EWF and eventually Eiffel Web Nino, then demonstrate it on a simple example. WebSocket is a web technology providing for bi-directional, full-duplex communications channels over a single TCP connection.
* See http://en.wikipedia.org/wiki/Websocket * See [http://en.wikipedia.org/wiki/Websocket](http://en.wikipedia.org/wiki/Websocket)
---- ----
# Usage of EWF # Usage of EWF
@@ -84,13 +84,13 @@ If you are a student, don't hesitate to pick one, or even suggest a new project,
* _Suggested by **Javier**_ * _Suggested by **Javier**_
* _Supervisor_: * _Supervisor_:
* _Suitability_: TODO * _Suitability_: TODO
* _Description_: Build a HAL browser to discover an API using HAL mediatype. The browser will be able to follow the links, and display the transmitted data. This could be a vision2 application inspired by http://haltalk.herokuapp.com/explorer/hal_browser.html#/. HAL stands for Hypertext Application Language see http://stateless.co/hal_specification.html. * _Description_: Build a HAL browser to discover an API using HAL mediatype. The browser will be able to follow the links, and display the transmitted data. This could be a vision2 application inspired by [http://haltalk.herokuapp.com/explorer/hal_browser.html#/](http://haltalk.herokuapp.com/explorer/hal_browser.html#/). HAL stands for Hypertext Application Language see [http://stateless.co/hal_specification.html](http://stateless.co/hal_specification.html).
## Collection-JSON browser ## Collection-JSON browser
* _Suggested by **Javier**_ * _Suggested by **Javier**_
* _Supervisor_: * _Supervisor_:
* _Suitability_: TODO * _Suitability_: TODO
* _Description_: Build a Collection/JSON browser to discover an API using Collection/JSON mediatype. The browser will be able to follow the links, and display the transmitted data. This could be a vision2 application inspired by http://haltalk.herokuapp.com/explorer/hal_browser.html#/. Collection+JSON is a JSON-based read/write hypermedia-type, see http://www.amundsen.com/media-types/collection/ * _Description_: Build a Collection/JSON browser to discover an API using Collection/JSON mediatype. The browser will be able to follow the links, and display the transmitted data. This could be a vision2 application inspired by [http://haltalk.herokuapp.com/explorer/hal_browser.html#/](http://haltalk.herokuapp.com/explorer/hal_browser.html#/). Collection+JSON is a JSON-based read/write hypermedia-type, see [http://www.amundsen.com/media-types/collection/](http://www.amundsen.com/media-types/collection/)
## Build a simple CMS with EWF ## Build a simple CMS with EWF
* _Suggested by **Jocelyn**_ * _Suggested by **Jocelyn**_
@@ -119,7 +119,7 @@ If you are a student, don't hesitate to pick one, or even suggest a new project,
* _Suggested by **Javier**_ * _Suggested by **Javier**_
* _Supervisor_: * _Supervisor_:
* _Suitability_: TODO * _Suitability_: TODO
* _Description_: Use XHTML as a media type to for hypermedia API. See http://codeartisan.blogspot.com.ar/2012/07/using-html-as-media-type-for-your-api.html * _Description_: Use XHTML as a media type to for hypermedia API. See [http://codeartisan.blogspot.com.ar/2012/07/using-html-as-media-type-for-your-api.html](http://codeartisan.blogspot.com.ar/2012/07/using-html-as-media-type-for-your-api.html)
## Add support for Mediatype such as RSS, ATOM, ... ## Add support for Mediatype such as RSS, ATOM, ...
* _Suggested by **Jocelyn**_ * _Suggested by **Jocelyn**_
@@ -155,24 +155,24 @@ If you are a student, don't hesitate to pick one, or even suggest a new project,
* _Suitability_: TODO * _Suitability_: TODO
* _Description_: Design and build a Single Sign On implementation for Eiffel. That should include the authentication server, and at least one Eiffel client component (it would be convenient to also provide php, js, ...). In the same spirit, having Eiffel client for popular SSO server would be appreciated as well. * _Description_: Design and build a Single Sign On implementation for Eiffel. That should include the authentication server, and at least one Eiffel client component (it would be convenient to also provide php, js, ...). In the same spirit, having Eiffel client for popular SSO server would be appreciated as well.
* _Reference_: * _Reference_:
- http://en.wikipedia.org/wiki/Single_sign-on - [http://en.wikipedia.org/wiki/Single_sign-on](http://en.wikipedia.org/wiki/Single_sign-on)
- http://en.wikipedia.org/wiki/List_of_single_sign-on_implementations - [http://en.wikipedia.org/wiki/List_of_single_sign-on_implementations](http://en.wikipedia.org/wiki/List_of_single_sign-on_implementations)
## library: Template engine ## library: Template engine
* _Suggested by **Jocelyn**_ * _Suggested by **Jocelyn**_
* _Supervisor_: * _Supervisor_:
* _Suitability_: TODO * _Suitability_: TODO
* _Description_: Get inspired by any existing template engine, and build one for Eiffel, this should be easily usable within a web application. This could be inspired, or implementation of standard template engine, this way people can reuse existing content, or migrate easily their application to EWF. For inspiration, one can look at: * _Description_: Get inspired by any existing template engine, and build one for Eiffel, this should be easily usable within a web application. This could be inspired, or implementation of standard template engine, this way people can reuse existing content, or migrate easily their application to EWF. For inspiration, one can look at:
- http://www.smarty.net/ - [http://www.smarty.net/](http://www.smarty.net/)
- http://mustache.github.com/ - [http://mustache.github.com/](http://mustache.github.com/)
- http://en.wikipedia.org/wiki/Template_engine_(web) ... they are plenty of them, a comparison of the different engine would help. - [http://en.wikipedia.org/wiki/Web_template_system](http://en.wikipedia.org/wiki/Web_template_system) ... they are plenty of them, a comparison of the different engine would help.
* This is not specific to EWF, but it will be very useful in website context. * This is not specific to EWF, but it will be very useful in website context.
## library: Wikitext, markdown parser and render engine ## library: Wikitext, markdown parser and render engine
* _Suggested by **Jocelyn**_ * _Suggested by **Jocelyn**_
* _Supervisor_: * _Supervisor_:
* _Suitability_: TODO * _Suitability_: TODO
* _Description_: Build component to support (read and write, and why not convert), lightweight markup language (see http://en.wikipedia.org/wiki/Lightweight_markup_language) such as wikitext, markdown, and other. The component should be able to read/scan, but also produce an HTML output. Focus first on wikitext, and markdown since they seems to be the most popular. * _Description_: Build component to support (read and write, and why not convert), lightweight markup language (see [http://en.wikipedia.org/wiki/Lightweight_markup_language](http://en.wikipedia.org/wiki/Lightweight_markup_language)) such as wikitext, markdown, and other. The component should be able to read/scan, but also produce an HTML output. Focus first on wikitext, and markdown since they seems to be the most popular.
* Then , a nice addition would be to render those lightweight markup lang into Vision2 widget (not related to EWF, but could be useful to build (editor) desktop application) * Then , a nice addition would be to render those lightweight markup lang into Vision2 widget (not related to EWF, but could be useful to build (editor) desktop application)
## library: Web component to build HTML5 widget ## library: Web component to build HTML5 widget
@@ -195,16 +195,16 @@ If you are a student, don't hesitate to pick one, or even suggest a new project,
* _Suitability_: TODO * _Suitability_: TODO
* _Description_: TODO * _Description_: TODO
* Generic client that can be customized (see design in slide 12) * Generic client that can be customized (see design in slide 12)
* http://s3.amazonaws.com/cimlabs/Oredev-Hypermedia-APIs.pdf * [http://s3.amazonaws.com/cimlabs/Oredev-Hypermedia-APIs.pdf](http://s3.amazonaws.com/cimlabs/Oredev-Hypermedia-APIs.pdf)
* video http://vimeo.com/20781278 * video [http://vimeo.com/20781278](http://vimeo.com/20781278)
## Create a Client Cache based on Apache commons Client Cache. ## Create a Client Cache based on Apache commons Client Cache.
* _Suggested by **Javier**_ * _Suggested by **Javier**_
* _Supervisor_: * _Supervisor_:
* _Suitability_: TODO * _Suitability_: TODO
* _Description_: TODO * _Description_: TODO
* http://hc.apache.org/httpcomponents-client-ga/httpclient-cache/index.html * [http://hc.apache.org/httpcomponents-client-ga/httpclient-cache/index.html](http://hc.apache.org/httpcomponents-client-ga/httpclient-cache/index.html)
* http://labs.xfinity.com/benchmarking-the-httpclient-caching-module * [http://labs.xfinity.com/benchmarking-the-httpclient-caching-module](http://labs.xfinity.com/benchmarking-the-httpclient-caching-module)
## Add SSL support to Eiffel Net ## Add SSL support to Eiffel Net
* _Suggested by **Jocelyn**_ * _Suggested by **Jocelyn**_
@@ -231,9 +231,9 @@ If you are a student, don't hesitate to pick one, or even suggest a new project,
* _Supervisor_: * _Supervisor_:
* _Suitability_: TODO * _Suitability_: TODO
* _Description_: TODO * _Description_: TODO
* See: http://en.wikipedia.org/wiki/Edge_Side_Includes * See: [http://en.wikipedia.org/wiki/Edge_Side_Includes](http://en.wikipedia.org/wiki/Edge_Side_Includes)
---- ----
# Feel free to add new idea below this line # Feel free to add new idea below this line
---- ----
Use the following page [[Projects new suggestions]] to suggest new project, or request a feature. Use the following page [Projects new suggestions](./Projects new suggestions) to suggest new project, or request a feature.

9
doc/wiki/Request-and-response.md Normal file
View File

@@ -0,0 +1,9 @@
# Request
The class _WSF_REQUEST_ can be used to access data related to the HTTP request.
**TODO**: describe the request interface
# Response
The class _WSF_RESPONSE_ is the media to send data back to the client.
**TODO**: describe the response interface

3
doc/wiki/Router.md Normal file
View File

@@ -0,0 +1,3 @@
The primary goal of the router (class _WSF_ROUTER_) is to dispatch requests according to the request URI.
**TODO**: describe the router interface

3
doc/wiki/Tasks-Roadmap.md
View File

@@ -1,3 +1,4 @@
Check new roadmap wiki page: [roadmap](./roadmap)
## Future ## Future
* Focus on REST API * Focus on REST API
- Hypermedia API - Hypermedia API
@@ -31,5 +32,5 @@
* Installation scripts * Installation scripts
## Contributors ## ## Contributors ##
- See [[the collaboration page|Community-collaboration]] - See [the collaboration page](./Community-collaboration)

12
doc/wiki/Useful-links.md
View File

@@ -1,14 +1,14 @@
## Eiffel ## Eiffel
* http://www.scoop.it/t/eiffel-resources * [http://www.scoop.it/t/eiffel-resources](http://www.scoop.it/t/eiffel-resources)
* http://www.scoop.it/t/eiffel * [http://www.scoop.it/t/eiffel](http://www.scoop.it/t/eiffel)
## Hypermedia ## Hypermedia
* http://www.scoop.it/t/hyper-media-apis * [http://www.scoop.it/t/hyper-media-apis](http://www.scoop.it/t/hyper-media-apis)
* http://www.scoop.it/t/hypermedia-api * [http://www.scoop.it/t/hypermedia-api](http://www.scoop.it/t/hypermedia-api)
## ETags ## ETags
* http://www.mnot.net/blog/2007/08/07/etags * [http://www.mnot.net/blog/2007/08/07/etags](http://www.mnot.net/blog/2007/08/07/etags)
* http://bitworking.org/news/150/REST-Tip-Deep-etags-give-you-more-benefits * [http://bitworking.org/news/150/REST-Tip-Deep-etags-give-you-more-benefits](http://bitworking.org/news/150/REST-Tip-Deep-etags-give-you-more-benefits)

8
doc/wiki/Web-meeting-2012-09-18.md
View File

@@ -8,14 +8,14 @@
## Information ## Information
### When ? ### When ?
* Tuesday 18th of september, 19:00 - 20:00 UTC/GMT time (see 3rd time in http://www.doodle.com/8v2sekiyebp4dpyh) * Tuesday 18th of september, 19:00 - 20:00 UTC/GMT time (see 3rd time in [http://www.doodle.com/8v2sekiyebp4dpyh](http://www.doodle.com/8v2sekiyebp4dpyh))
### Where ? ### Where ?
Web meeting using webex Web meeting using webex
* Short url: http://goo.gl/wBz11 * Short url: [http://goo.gl/wBz11](http://goo.gl/wBz11)
* Long url: https://eiffel.webex.com/eiffel/j.php?ED=211265702&UID=0&PW=NZWNiMjBiZWIz&RT=MiMyMA%3D%3D * Long url: [https://eiffel.webex.com/eiffel/j.php?ED=211265702&UID=0&PW=NZWNiMjBiZWIz&RT=MiMyMA%3D%3D](https://eiffel.webex.com/eiffel/j.php?ED=211265702&UID=0&PW=NZWNiMjBiZWIz&RT=MiMyMA%3D%3D)
* Related Google group topic: https://groups.google.com/d/topic/eiffel-web-framework/A7ADPAT3nj8/discussion * Related Google group topic: [https://groups.google.com/d/topic/eiffel-web-framework/A7ADPAT3nj8/discussion](https://groups.google.com/d/topic/eiffel-web-framework/A7ADPAT3nj8/discussion)
## Agenda ## Agenda

4
doc/wiki/roadmap.md Normal file
View File

@@ -0,0 +1,4 @@
# Upcoming versions
# Current state: oct-2013
- check previous wiki page: [Tasks roadmap](./Tasks roadmap)