On Wed, Jul 24, 2013 at 3:55 PM, Sanjiva Weerawarana <[email protected]>wrote:
> Sumedha that's not natural from the HTTP point of view .. that's why I > believe it was not there originally. (Or was it? I can't remember for > sure.) > This has been there. >From an HTTP point of view a fault is a 500 response .. so if the back end > fails for some reason it should generate a 500 message thru the response > path. Can we not model it that way? > eg: If the backend is a SOAP endpoint, the failure would come through the fault sequence. IMO that is more in alignment with how other endpoints work. API element is just a wrapper to provide HTTP nature to outside world. Isn't that a correct way to explain the behavior? IMO that's a lot more accurate from an HTTP point of view for APIs. > > Sanjiva. > > > On Tue, Jul 23, 2013 at 12:15 PM, Sumedha Rubasinghe <[email protected]>wrote: > >> HTTP nature is offered to outside through the API. >> >> Fault sequence here helps us to call the backends(might not be a HTTP >> service at all), figure out if it sends an error response & then send a >> proper HTTP error to front end HTTP client (expecting a standard HTTP error >> code). >> >> >> On Tue, Jul 23, 2013 at 11:22 AM, Samisa Abeysinghe <[email protected]>wrote: >> >>> In the generated API we have a fault sequence. >>> >>> In a DevStudio review, the question came, if this was correct to have a >>> fault sequence, given the HTTP semantics here. >>> >>> <api >>> xmlns="http://ws.apache.org/ns/synapse<http://www.google.com/url?q=http%3A%2F%2Fws.apache.org%2Fns%2Fsynapse&sa=D&sntz=1&usg=AFQjCNHXEm-DVy-kXjma9HiDSOzvmv4DoA>" >>> name="foo" context="/foo"> >>> <resource methods="GET"> >>> <inSequence> >>> <log/> >>> </inSequence> >>> <outSequence> >>> <log/> >>> </outSequence> >>> <faultSequence> >>> <log/> >>> </faultSequence> >>> </resource> >>> </api> >>> >>> -- >>> >>> Thanks, >>> Samisa... >>> >>> Samisa Abeysinghe >>> VP Engineering >>> WSO2 Inc. >>> http://wso2.com >>> http://wso2.org >>> >>> _______________________________________________ >>> Architecture mailing list >>> [email protected] >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>> >>> >> >> >> -- >> /sumedha >> b : bit.ly/sumedha >> >> _______________________________________________ >> Architecture mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > Sanjiva Weerawarana, Ph.D. > Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/ > email: [email protected]; phone: +94 11 763 9614; cell: +94 77 787 6880 | +1 > 650 265 8311 > blog: http://sanjiva.weerawarana.org/ > > Lean . Enterprise . Middleware > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- /sumedha b : bit.ly/sumedha
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
