Open GoogleCodeExporter opened 9 years ago
This will address 3 points in the design.
1) In handlers.cc a SOAP request would be handed off to a SOAP handler. The
SOAP handler would parse the
XML SOAP envelope, and would create the response SOAP envelope. For instance,
if a query returned an error
result (40x), this would be translated into the SOAP envelope but the actual
HTTP response could still be 200.
2) The request, parsed from the envelope, would be represented as a
query_source.
3) The final response includes both a standard envelope and a (custom) message.
Original comment by john.david.duncan
on 8 Nov 2007 at 9:31
Work on this feature will be scheduled if someone requests and sponsors it.
Original comment by john.david.duncan
on 28 Dec 2007 at 5:32
This could also be done as a Summer of Code project.
Original comment by john.david.duncan
on 26 Mar 2008 at 3:00
Here's an alternate architecture. This may not perform as well, but would be
more independent.
Essentially, a separate module (e.g. mod_ndb_soap) handles the SOAP request.
This module generates a faux
HTTP request, which it hands in to mod_ndb as a subrequest.
This idea leads to yet another... that "mod_ndb_soap" is implemented in a
high-level language like PHP, and
either uses the current subrequest interface or the cursor interface proposed
in issue #59 to call down.
Original comment by john.david.duncan
on 26 Mar 2008 at 3:06
I can work on this issue as a Summer of Code project.
Original comment by makarov...@gmail.com
on 2 Apr 2009 at 5:43
I am ready to do work on this project. Becouse it suits for my area of interest.
Original comment by ranjanmi...@gmail.com
on 3 Apr 2009 at 10:59
Attachments:
Original issue reported on code.google.com by
john.david.duncan
on 8 Nov 2007 at 9:22