This is an automated notification sent by LCG Savannah.
It relates to:
task #10637, project CDS Invenio
==============================================================================
LATEST MODIFICATIONS of task #10637:
==============================================================================
Update of task #10637 (project cdsware):
Status: None => Done
Percent Complete: 0% => 100%
Assigned to: None => skaplun
Open/Closed: Open => Closed
==============================================================================
OVERVIEW of task #10637:
==============================================================================
URL:
<http://savannah.cern.ch/task/?10637>
Summary: Simulating mod_python request object under mod_wsgi
Project: CDS Invenio
Submitted by: skaplun
Submitted on: 2009-07-29 15:10
Should Start On: 2009-07-29 00:00
Should be Finished on: 2009-07-29 00:00
Category: WebStyle
Priority: 7 - High
Status: Done
Privacy: Public
Percent Complete: 100%
Assigned to: skaplun
Open/Closed: Closed
Discussion Lock: Any
Effort: 1000.00
_______________________________________________________
As now made clear by on mod_python mailing list:
<http://mailman.modpython.org/pipermail/mod_python/2009-July/026286.html>
migrating away of the no-more maintained mod_python is a necessary step for
Invenio.
A migration from mod_python to mod_wsgi+web.py framework might be the
solution.
For this the first step is to implement a simulation of the mod_python
request object under mod_wsgi, in order for Invenio to be compatibile with
mod_wsgi without its web_interface modules to immediately rewritten.
Currently the usage of mod_python request object in Invenio is as follows:
$ egrep -R "\breq\.[a-z_A-Z]+\b" --include=*.py * -oh | sort | uniq -c | sort
-nr
184 req.write
38 req.content_type
30 req.send_http_header
27 req.headers_out
20 req.unparsed_uri
19 req.uri
19 req.headers_in
18 req.subprocess_env
18 req.args
14 req.get_remote_host
13 req.argd
12 req.form
11 req._user_info
10 req.header_only
9 req.status
9 req.err_headers_out
9 req.connection
7 req.add_common_vars
5 req.sendfile
4 req.set_content_length
4 req.is_https
3 req.method
3 req.has_key
2 req._session
2 req.hostname
2 req.filename
2 req.encoding
2 req.add_header
1 req.sent_bodyct
1 req.read
1 req.next
1 req.log_error
1 req.journal_defaults
1 req.info
1 req.flush
1 req._content_type_set
1 req.bytes_sent
1 req.allow_methods
which can be a good guide of a possible order of methods/attribute to
simulate
_______________________________________________________
Carbon-Copy List:
CC Address | Comment
------------------------------------+-----------------------------
2195 | -SUB-
==============================================================================
This item URL is:
<http://savannah.cern.ch/task/?10637>
_______________________________________________
Message sent via/by LCG Savannah
http://savannah.cern.ch/
