<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Tcp on Blogfolio Najib</title>
		<link>https://najib.id/en/tags/tcp/</link>
		<description>Recent content in Tcp on Blogfolio Najib</description>
		<generator>Hugo</generator>
		<language>en-US</language>
		
		
		
			<copyright>This work is licensed under a Creative Commons Attribution-NonCommercial 4.0 International License.</copyright>
		
		
			<lastBuildDate>Fri, 09 Oct 2026 16:37:02 +0700</lastBuildDate>
		
			<atom:link href="https://najib.id/en/tags/tcp/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Building a TCP Listener for GPS Devices in Go</title>
				<link>https://najib.id/en/writing/2026/tcp-listener-gps-go/</link>
				<pubDate>Tue, 22 Sep 2026 00:00:00 +0000</pubDate>
				<guid>https://najib.id/en/writing/2026/tcp-listener-gps-go/</guid>
				<description>&lt;p&gt;Picture 500 GPS trackers connected to your server simultaneously, each streaming location data every 10–30 seconds, while others only emit a quiet heartbeat when parked. These connections stay alive for hours, occasionally drop without saying goodbye, and sometimes deliver fragmented data in bursts.&lt;/p&gt;&#xA;&lt;p&gt;If you come from the world of HTTP APIs, where one neat request yields one neat response, stepping into TCP feels like moving from delivering individual courier parcels to running a bustling sorting office where the mail never stops flowing.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Understanding GPS Protocols: How Tracker Devices Communicate</title>
				<link>https://najib.id/en/writing/2026/memahami-gps-protocol/</link>
				<pubDate>Tue, 08 Sep 2026 00:00:00 +0000</pubDate>
				<guid>https://najib.id/en/writing/2026/memahami-gps-protocol/</guid>
				<description>&lt;p&gt;When I was first trusted to build and maintain a backend for hundreds of GPS trackers, I assumed it was just a matter of writing a standard REST API: the device fires off a &lt;code&gt;POST /api/location&lt;/code&gt; with JSON, the server saves it to the database, and we&amp;rsquo;re done.&lt;/p&gt;&#xA;&lt;p&gt;I was dead wrong. (The full story of why that backend was eventually migrated from Laravel to Go, across 370+ endpoints, is documented in my &lt;a href=&#34;https://najib.id/en/writing/2026/hijrah-backend-01/&#34;&gt;Hijrah Backend narrative series&lt;/a&gt;. The series you are reading right now is the tutorial counterpart: rebuilding the architecture from scratch, complete with code you can follow along with.)&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
