<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Dapr PHP SDK on Dapr Docs</title><link>https://v1-18.docs.dapr.io/developing-applications/sdks/php/</link><description>Recent content in Dapr PHP SDK on Dapr Docs</description><generator>Hugo</generator><language>en</language><atom:link href="https://v1-18.docs.dapr.io/developing-applications/sdks/php/index.xml" rel="self" type="application/rss+xml"/><item><title>Custom Serialization</title><link>https://v1-18.docs.dapr.io/developing-applications/sdks/php/php-serialization/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://v1-18.docs.dapr.io/developing-applications/sdks/php/php-serialization/</guid><description>&lt;p>Dapr uses JSON serialization and thus (complex) type information is lost when sending/receiving data.&lt;/p>
&lt;h2 id="serialization">Serialization&lt;/h2>
&lt;p>When returning an object from a controller, passing an object to the &lt;code>DaprClient&lt;/code>, or storing an object in a state store,
only public properties are scanned and serialized. You can customize this behavior by implementing &lt;code>\Dapr\Serialization\ISerialize&lt;/code>.
For example, if you wanted to create an ID type that serialized to a string, you may implement it like so:&lt;/p></description></item></channel></rss>