<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Networking on Coyote Time</title>
    <link>https://blog.jonmikeys.com/tags/networking/</link>
    <description>Recent content in Networking on Coyote Time</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 14 Aug 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://blog.jonmikeys.com/tags/networking/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>API Programming Through HTTP: The Rules I Lean on in Game Code</title>
      <link>https://blog.jonmikeys.com/posts/api-programming-through-http/</link>
      <pubDate>Fri, 14 Aug 2026 00:00:00 +0000</pubDate>
      <guid>https://blog.jonmikeys.com/posts/api-programming-through-http/</guid>
      <description>A practical guide to calling HTTP APIs from game code without making retries, auth, or failure handling a mess.</description>
    </item>
    <item>
      <title>Mirror Multiplayer, Part 1: Authority First, RPCs Second</title>
      <link>https://blog.jonmikeys.com/posts/mirror-multiplayer-part-1-authority-first-rpcs-second/</link>
      <pubDate>Tue, 21 Jul 2026 00:00:00 +0000</pubDate>
      <guid>https://blog.jonmikeys.com/posts/mirror-multiplayer-part-1-authority-first-rpcs-second/</guid>
      <description>A practical way to structure Mirror games so the server owns the rules, clients send intent, and state sync stays boring.</description>
    </item>
  </channel>
</rss>
