This is an automated notification sent by LCG Savannah.
It relates to:
task #8889, project CDS Invenio
==============================================================================
OVERVIEW of task #8889:
==============================================================================
URL:
<http://savannah.cern.ch/task/?8889>
Summary: Generic WEBAPI interface
Project: CDS Invenio
Submitted by: skaplun
Submitted on: 2009-01-26 16:41
Should Start On: 2009-01-26 00:00
Should be Finished on: 2009-01-26 00:00
Category: WebStyle
Priority: 1 - Later
Status: None
Privacy: Private
Percent Complete: 0%
Assigned to: None
Open/Closed: Open
Discussion Lock: Any
Effort: 0.00
_______________________________________________________
One of the things are missing in WebSubmit is the ability to query the server
ala Ajax while presenting some
form to the user (imagine if we would implement publiline completely via
WebSubmit, what would be needed is a dynamic form that let the
referee/chairman/... choose from a dynamically generated list, the
peer-reviewer).
Given that WebSubmit is already heavily based on Javascript why not than let
it use Ajax?
Here it comes a generic webservice infrastructure where e.g.:
http://cdsweb.cern.ch/webapi?id=choose_reviewer&egroup=ATLAS&startswith="Don";
would return a JSon object with the list of all the ATLAS possible author
with a name starting with Don. This would be called by Javascript inside a
form to let the user (who has typed Don) to choose from a drop down menu the
next
authors to add)
The generic webservice might be built with the usual plugin fashion, where a
plugin should simply implement a function receiving some parameters (coming
from the form-GET parameters) and should return a Python object suitable to
be encoded in Json (which is automatically understood by Javascript)...
This interface might be used anywhere is needed some Ajax webservice.
In Invenio some WEBAPI already exists (e.g. /search?of=xm, bibknowledge,
future bibedit, the suggestion engine) (and they even already return AJAX
sometimes).
This webapi handler might redirect directly to this already existing specific
WEBAPIS, thus behaving as a centralized interface to find all of them (in this
case the output is not automatically json), plus it would support
administrator-designed new APIs, by dropping simple python functions into a
given folder, that would automatically transform them into AJAX-ish APIs (by
transforming into JSON their output).
The framework might give the user a standard way to restrict access and to
provide errors, ...
_______________________________________________________
Carbon-Copy List:
CC Address | Comment
------------------------------------+-----------------------------
2195 | -SUB-
==============================================================================
This item URL is:
<http://savannah.cern.ch/task/?8889>
_______________________________________________
Message sent via/by LCG Savannah
http://savannah.cern.ch/
