<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Error/Exception on Game Server Services | Docs</title>
    <link>/articles/tech/error/</link>
    <description>Recent content in Error/Exception on Game Server Services | Docs</description>
    <generator>Hugo</generator>
    <language>en</language>
    <atom:link href="/articles/tech/error/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Implementation Patterns for Error Handling</title>
      <link>/articles/tech/error/pattern/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/articles/tech/error/pattern/</guid>
      <description>In network feature implementation using GS2, error handling directly impacts game stability and user experience (UX). Here are some practical implementation patterns that go beyond simple exception catching.&#xA;1. Error Classification and Handling Policy GS2 exceptions can be broadly classified into three categories based on their nature.&#xA;Category Applicable Exceptions (Example) Handling Policy Transient Errors InternalServerError, ServiceUnavailable, RequestTimeout Automatic Retry. If it fails after several attempts, display an error dialog. Logic/Configuration Errors BadRequest, NotFound Errors to be resolved during development.</description>
    </item>
  </channel>
</rss>
