Re: soup, glib2/libxml2

Scott Hutton <[email protected]> Thu, 29 Aug 2002 13:52:32 -0700 (PDT)
Newsgroups gmane.comp.gnome.ximian.soup
Message-ID <Pine.LNX.4.44.0208291340560.16310-100000@habanero.gibraltarsoft.com>
Today, Alex Graveley wrote:
| On Wed, 2002-08-28 at 14:19, Scott Hutton wrote:
| > Today, Joe Shaw wrote:
| > | Yep.  My patch (and the latest tarball of xmlrpc-c) are here:
| > | 
| > |         http://primates.ximian.com/~joe/xmlrpc-c
| > 
| > Speaking of patches, I sent in some patches and raised some issues with
| > faulty fault handling back in May.  Has Soup development resumed or moved
| > on to another maintainer at Ximian (Alex appears to have disappeared on
| > the list)?  Should I resubmit those patches?
| 
| Feel free to resubmit, but you mention that your patch was very broken
| with regards to modifying resultcode values, so it won't go in until its
| fixed correctly.  The xml child handling changes seem broken as well. 

It was broken with respect to the way that Soup handles HTTP responses.
Soup treats all 500 responses from the server as server errors.  However,
faults are legitimately 500's with an XML payload.  I indicated that some
"big picture" folks (i.e., Ximian) needed to address that issue before
this could be patched properly.  That's pretty much where the discussion
stopped.  As a stopgap, my patch allowed 500's to be treated as valid,
worth-examining responses, whether or not they contained a valid SOAP
response.

Admittedly, I don't like this aspect of the SOAP protocol, but it's
probably there to stay.  MS SOAP handles this correctly, which certainly
threw *me* for a loop -- it took some work to get SOAP::Lite + Apache
to issue faults correctly, since Apache is keen on intercepting error
responses and replacing with custom error documents.

 -Scott


_______________________________________________
Soup-list maillist  -  [email protected]
http://lists.ximian.com/mailman/listinfo/soup-list