backup/EWF

Files

Jocelyn Fiat b541efcc8f Now WGI_RESPONSE.set_status_code (..) has a new argument to pass optional custom reason phrase.

This is a minor breaking change (but prior to the first release, so acceptable)
   And then it is now possible to precise a custom reason phrase (useful for 4xx and 5xx response)

At the WSF_RESPONSE level, the status code is now sent only when the header are sent.
thus, it is possible to change the status code as long as no header is sent.
(in the future, we should also try to delay the sending of headers)

Removed WGI_RESPONSE.put_header_lines (..) which was not used, and WGI is not meant to provide such user friendly features
Now this is available directly on WSF_RESPONSE

2012-04-12 11:19:41 +02:00

connectors

Now WGI_RESPONSE.set_status_code (..) has a new argument to pass optional custom reason phrase.

2012-04-12 11:19:41 +02:00

doc

First integration of the new GW_ design more centralized on connector, and does not require specific feature on GW_APPLICATION depending on the connector.

2011-07-12 11:53:00 +02:00

examples/hello_world

Fixing compilation of specific example using the WGI connector directly

2012-03-20 12:15:45 +01:00

specification

Now WGI_RESPONSE.set_status_code (..) has a new argument to pass optional custom reason phrase.

2012-04-12 11:19:41 +02:00

src

Now WGI_RESPONSE.set_status_code (..) has a new argument to pass optional custom reason phrase.

2012-04-12 11:19:41 +02:00

First integration of the new GW_ design more centralized on connector, and does not require specific feature on GW_APPLICATION depending on the connector.

2011-07-12 11:53:00 +02:00

default.7z

Applied recent changes on WGI_ and WSF_

2011-10-21 16:58:23 +02:00

ewsgi_spec-safe.ecf

Tried to reduce gap between both EWSGI proposals

2011-08-01 16:41:16 +02:00

ewsgi_spec.ecf

Tried to reduce gap between both EWSGI proposals

2011-08-01 16:41:16 +02:00

ewsgi-safe.ecf

Updating EWSGI specification classes

2012-03-19 15:06:50 +01:00

ewsgi.ecf

Updating EWSGI specification classes

2012-03-19 15:06:50 +01:00

license.lic

Major renaming, adopt the WSF_ prefix for all classes under "wsf", and simplify some class names

2012-03-16 09:49:41 +01:00

README.md

Renamed "ext" folder as "contrib" folder and reorganized a little bit

2011-11-17 15:50:30 +01:00

README.md

Eiffel Web Server Gateway Interface

Overview

The main goal of this library is to provide a common layer on top of many different connectors. A connector is a library used for the integration of Eiffel web server application with an underlying httpd server technology such as CGI, libFCGI, or even standalone Eiffel Web Nino (which is a httpd server written in Eiffel).

Then one can build an Eiffel web service compliant with EWSGI specification, and thus with the same code (or almost), this could be compiled to run on any available connectors.

README.md

Eiffel Web Server Gateway Interface

Overview

Usage