ListTree - share and edit lists of lists
about list tree
feedback
create a new list tree

list tree: wsgi2

 
discussion tree about wsgi 2   [edit]
link: http://listtree.appspot.com/wsgi2/wsgi2 [slides]

This listtree is for archiving discussion points about the next generation of WSGI.

[6 responses] [add response] aaron
 
 
what is good about WSGI 1?   [edit]
link: http://listtree.appspot.com/wsgi2/0P4qwWk4OihGqaXHJsBfqw [slides]

What are the good points of WSGI 1 which should be preserved?

[2 responses] [add response] aaron
 
what's bad about WSGI 1?   [edit]
link: http://listtree.appspot.com/wsgi2/li_aQSbMZHfIos77R2iqHQ [slides]

What are the deficiences of WSGI 1 and why do they cause problems?

[1 responses] [add response] aaron
 
Good aspects of other systems?   [edit]
link: http://listtree.appspot.com/wsgi2/RoNvf_QpBIc6AvhejNj4oA [slides]

What are good aspects of other systems that would be good to have in WSGI 2?

[no responses] [add response] aaron
 
What's bad about other systems   [edit]
link: http://listtree.appspot.com/wsgi2/$ipbwP39AJrNcz1Fh0jsGw [slides]

What aspects of other approaches should be avoided?

[no responses] [add response] aaron
 
design ideas or prototypes   [edit]
link: http://listtree.appspot.com/wsgi2/_LD4jCZnhDP_hG7sLnfsCw [slides]

What are some alternative designs for WSGI 2?  Are there any prototype reference implementations which could be adopted or modified?

[no responses] [add response] aaron
 
Move to bless Graham's WSGI 1.1 as official spec   [edit]
link: http://listtree.appspot.com/wsgi2/ICvaujouPxb2gfEhDS_aiw [slides]
"James Y Knight"
I move to bless mod_wsgi's definition of WSGI 1.1 [1] as the official definition of WSGI 1.1, which describes how to implement WSGI adapters for both Python 2.x and 3.x. It may not be perfect, but, it's been implemented twice, and seems ot have no fatal flaws (it doesn't do any lossy transforms, so any issues are irritations at worst). The basis for this definition is also described in the "WSGI 1.0 Ammendments" [2] page.

The definitions as they stand are clear enough to understand and implement, but not currently in spec-worthy language. (e.g. it says "should" and "may" in a colloquial fashion, but actually means MUST in some places and SHOULD in others, as defined by RFC 2119)

Thus, I'd like to suggest that Graham (if he's willing?) should reformat the "Definition"/"Ammendments" as an actual diff against the current PEP 333. Then, I will recommend adopting that document as an actual standard WSGI 1.1, to replace PEP 333.

This discussion has gone on long enough, and it doesn't really matter as much to have the perfect API, as it does to have a standard.

James

[1] http://code.google.com/p/modwsgi/wiki/SupportForPython3X [2] http://www.wsgi.org/wsgi/Amendments_1.0

agree, disagree etc below
[1 responses] [add response] aaron


go to top of list tree: http://appspot.listtree.com/wsgi2
view the whole list tree on one page: http://appspot.listtree.com/wsgi2/wsgi2/all
outline; dump as xml