Planning, roadmap, ... todo

[Jocelyn Fiat]

Hi all, users, developpers, contributors, others,

We are working on building a roadmap (in order to plan future developments, priorities ... and so on, and mainly to better manage team collaboration)
The goal is
- find out what is missing for current v0.2 (not yet announced), we could still include some last minutes changes such as typo correction, documentation, ...
- plan next release v0.3
- and forcast future dev for v0.4 and after

Thus we would like you to contribute on this by suggesting entries, and comments
So far, Javier prepared a first contribution, please comment and suggest entries for EWF

------

TODO list

- Add support for CONNEG  (Content Negociation)

- Add support for OAuth (Client/Server)

- Add support for HTML as media type for expressing APIs 

• http://codeartisan.blogspot.com.ar/2012_07_01_archive.html
• http://codeartisan.blogspot.com.ar/2012_08_01_archive.html

- Add WebSocket support.

- improve implementation to support HTTP 1.0 and HTTP 1.1

 

Improvements

- Documentation for Kernel, Libraries

- Getting started with EWF

- Hypermedia libraries (HAL, CJ)

- Add test cases.

- Set up a Continuous Integration Server

- Create a cool web site for EWF.

- Improve the existing examples, add new ones.

Eiffel Web Nino

  Add test cases

  Add persistent connections support.

  Add configuration support (maybe using JSON) 

  Review the HTTP 1.1 spec and try to follow it.  

  Add documentation.

--------------

On my side, I would add some website building related tasks
- Continue work on experimental CMS
- OpenID
- Integrate a popular Javascript framework (such as JQuery, and JQueryUI) to enable building easily website using JS
- Add one Template Engine
- Build wizard tool to help generating code for REST, Website, ... application.

That's already a lot, but please send suggestion, then we will try to build a first roadmap , and eventually have a webmeeting to finalize it.

[Colin Adams]

On 10 January 2013 14:13, Jocelyn Fiat <jocely...@gmail.com> wrote:

 

Eiffel Web Nino

  Add test cases

  Add persistent connections support.

  Add configuration support (maybe using JSON) 

  Review the HTTP 1.1 spec and try to follow it.  

What about HTTP 1.0? Or are we just supposed to use Apache mod_proxy for 1.0 clients? 

 

[Jocelyn Fiat]

You are right

Differences between 1.0 and 1.1

ref: http://www8.org/w8-papers/5c-protocols/key/key.html (same as http://www2.research.att.com/~bala/papers/h0vh1.html )

ref: http://stackoverflow.com/questions/246859/http-1-0-vs-1-1/247026#247026

We should have a wiki page with all the 1.0 and 1.1 points, and see which one are supported

I guess they can be categorized into 3 main sets related to

C - connectors (nino, cgi, fcgi, ..) and underlying servers (nino, apache, nginx, ...)

F - framework WSF

A - application itself

Probably, some part can be handled by several layer ... either C, F or A

Any one has time and will, to build such table, to see if EWF support 1.0 and 1.1 ?

-- Jocelyn

--
--
You received this message because you are subscribed to the Google
Groups "Eiffel Web Framework" group.
 
To post to this group, send email to
eiffel-web...@googlegroups.com
To unsubscribe from this group, send email to
eiffel-web-frame...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/eiffel-web-framework
 
See the site for the Eiffel-Web-Framework project at
https://github.com/Eiffel-World/Eiffel-Web-Framework
 
 
 

[Olivier Ligot]

Hi,

Le jeudi 10 janvier 2013 15:13:42 UTC+1, Jocelyn Fiat a écrit :

That's already a lot, but please send suggestion, then we will try to build a first roadmap , and eventually have a webmeeting to finalize it.

On my side, I'm working on an initial support for the Cross-Origin Resource Sharing specification.

Here is the pull request (note that it hasn't been merged yet as I have to split the PR in smaller patches): https://github.com/EiffelWebFramework/EWF/pull/22

Olivier

[Jocelyn Fiat]

Hi Olivier,

I am working on find a nice solution of WSF_RESPONSE an delayed http header transfert.
When I have it, I will come back to you, and your CORS contribution.

-- Jocelyn

[Olivier Ligot]

Ok, fine.