leftyer/firefly
1
0
Fork 0
mirror of https://gitee.com/9miao/firefly.git synced 2025-12-06 15:09:13 +08:00
Code Issues Packages Projects Releases Wiki Activity

update README.md

Browse Source
This commit is contained in:
9miao Mobile Game
2013-11-13 10:12:41 +08:00
parent 1d621b40eb
commit 7a725f194e
1 changed files with 8 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
README.md
View File

@@ -14,7 +14,7 @@
<header class="entry-header">
<h1 class="entry-title">What's Firefly Game Server Framework？</h1>
</header><!-- .entry-header -->
</header>
<div class="entry-content">
<p align="left">&nbsp; &nbsp; &nbsp; &nbsp; Firefly is a free, open source, stable and rapid expansion, to "hot update" distributed game server side framework。Written in Python, based on the Twisted framework development。Firefly's design philosophy is to "let developers focus on front-end"，It includes a development framework and database caching services, and other basic services game servers，Save a lot of game developers working hours，Truly allows the user to focus on gameplay logic。It can be used to build a custom distributed architecture, only need to modify the configuration file to the appropriate。</p>
@@ -28,7 +28,7 @@
<li>There are dozens of basic gameplay system modules assembled using (v1.3.0 available)；</li>
</ul>
<p align="left"><strong>Frameworks introduced</strong></p>
<p align="left"><a href="http://firefly.9miao.com/wp-content/uploads/2013/08/123.jpg"><img class="alignnone wp-image-40" alt="123" src="./9miao_files/123.jpg" width="601" height="441"></a></p>
<p align="left"><a href="http://firefly2.9miao.com/wp-content/uploads/2013/08/123.jpg"><img class="alignnone wp-image-40" alt="123" src="./9miao_files/123.jpg" width="601" height="441"></a></p>
<ul>
<li>management, firefly is a multi-process, distributed game server。So each game server (process) management and extensions are firefly very important part of the framework by abstracting the server extensions very easy。</li>
<li>Network，Client connects communications, server inter-process communication, etc. constitute the entire game framework in the context，All games in this context processes are built on。Communication with the client uses a request / response style, so by the client's request, the server will give the appropriate response，The server can also take the initiative to push the message broadcast to the client。These requests are based on a request instruction number。（Such as defining 101 for the landing instructions）communication between the server process using the asynchronous callback method, thus reducing the inter-process communication in the network time-consuming。</li>
@@ -36,18 +36,18 @@
</ul>
<p align="left"><strong>Framework for thinking</strong><b></b></p>
<p align="left"><b>&nbsp; &nbsp; &nbsp; &nbsp;&nbsp;</b>A basic server that is running a non-stop applications。In a distributed game server, we need to have a server function, listen for client connections, monitor other services processes messages to connect to other service process，Some require a database connection and caching services。As shown</p>
<p align="left">&nbsp;<a href="http://firefly.9miao.com/wp-content/uploads/2013/08/234.jpg"><img class="alignnone size-full wp-image-41" alt="234" src="./9miao_files/234.jpg" width="552" height="401"></a></p>
<p align="left">&nbsp;<a href="http://firefly2.9miao.com/wp-content/uploads/2013/08/234.jpg"><img class="alignnone size-full wp-image-41" alt="234" src="./9miao_files/234.jpg" width="552" height="401"></a></p>
<p align="left">net connect Handle client connections，Other news monitoring service process root，node to connect to other service process，db database，“cache” database，cache 。Do they need to listen for client connections, whether listening other service processes messages, etc. This is all can be configured in config.json,Including the name of the server as well as the various connections between each server。So you can customize their own distributed architecture。</p>
</div><!-- .entry-content -->
</div>
</article><!-- #post-31 -->
</article>
</div><!-- #content -->
</div><!-- #primary -->
</div>
</div>
</div><!-- #main -->
</div>
</div>