<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Appendix on Apache Dubbo</title><link>https://deploy-preview-3199--dubbo.netlify.app/en/overview/reference/pixiu/other/user/appendix/</link><description>Recent content in Appendix on Apache Dubbo</description><generator>Hugo</generator><language>en</language><atom:link href="https://deploy-preview-3199--dubbo.netlify.app/en/overview/reference/pixiu/other/user/appendix/index.xml" rel="self" type="application/rss+xml"/><item><title>HTTP to Dubbo Default Conversion Protocol</title><link>https://deploy-preview-3199--dubbo.netlify.app/en/overview/reference/pixiu/other/user/appendix/http-to-dubbo-default-stragety/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://deploy-preview-3199--dubbo.netlify.app/en/overview/reference/pixiu/other/user/appendix/http-to-dubbo-default-stragety/</guid><description>&lt;h1 id="background">Background&lt;/h1>
&lt;p>​ By providing a unified service provider view through Http, users need not worry about backend Dubbo service version differences or protocol differences. They just need to pass RPC call parameters in an HTTP request to complete an RPC call, simplifying backend service design complexity by implementing HTTP calls to backend Dubbo services.&lt;/p>
&lt;h1 id="purpose">Purpose&lt;/h1>
&lt;p>​ To unify the format of HTTP calls to backend Dubbo services, facilitating gateway products to achieve HTTP-to-Dubbo call conversion and enhancing the integration of Dubbo with the gateway.&lt;/p></description></item></channel></rss>