<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Polish on Percona Community</title><link>https://percona.community/talk_tags/polish/</link><description>Recent content in Polish on Percona Community</description><generator>Hugo</generator><language>en-us</language><copyright>© Percona Community. MySQL, InnoDB, MariaDB and MongoDB are trademarks of their respective owners.</copyright><atom:link href="https://percona.community/talk_tags/polish/index.xml" rel="self" type="application/rss+xml"/><item><title>Hosting Someone Else's App: Iframe Choreography</title><link>https://percona.community/talks/2026/2026-11-18-hosting-someone-else-s-app-iframe-choreography/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://percona.community/talks/2026/2026-11-18-hosting-someone-else-s-app-iframe-choreography/</guid><description>&lt;p&gt;Most frontend architecture talks assume you control the whole page. This one doesn&amp;rsquo;t. Percona Monitoring and Management (PMM) ships a React/TypeScript shell that owns routing, navigation, and auth — and then embeds an entire third-party application, Grafana, inside an iframe it doesn&amp;rsquo;t control the internals of. The two apps have to feel like one product: shared theme, shared navigation, shared login state, no visible seam.&lt;/p&gt;&#10;&lt;p&gt;This talk walks through how that&amp;rsquo;s actually built: a custom CrossFrameMessenger that turns postMessage into typed, promise-based RPC calls with timeouts and listener lifecycles; and the handshake that gates showing the iframe until the guest app has actually finished loading. I&amp;rsquo;ll cover the race conditions this design has to defend against, how you test cross-frame code without an end-to-end browser suite for everything, and where the abstraction leaks.&lt;/p&gt;</description></item></channel></rss>