在Python中重命名一个目录中的多个文件[duplicate](Rename multiple files in a directory in Python [duplicate])

 要详细说明driushkin的答案，您应该使用远程过程调用（RPC）和事件队列。 这类似于您发布的图像，其中每个数据包代表一个“命令”或带有一些参数的RPC（即移动方向）。 您还需要一个事件队列来确保按顺序和按时执行RPC。 这将需要时间戳或帧计数来执行每个命令（在未来的某个时间点，以简单的方案）和同步手表（第二次世界大战风格）。 
 
 您可能会注意到此方案中的一个关键弱点：由于网络延迟，恶意用户等原因，RPC消息可能会延迟（应在应用之后到达）。在一个简单的方案中，会丢弃延迟的RPC。 这很好，因为所有客户端（甚至是发起人！）等待服务器在执行之前发送RPC（如果原始客户端没有等待服务器消息，他的游戏状态将与服务器不同步，并且您的游戏将被打破）。 
 
 考虑滞后对这种方案的影响。 假设客户端A到服务器的延迟是100毫秒，返回旅程也是100毫秒。 这意味着客户端输入如下： 
 
 
 
 客户端A按键，并将RPC发送到服务器， 但不在本地添加 （0ms） 
 
 
 服务器接收并重播RPC（100ms） 
 
 
 客户端A收到他自己的事件，现在最终将其添加到他的事件队列中进行处理（200ms） 
 
 
 正如您所看到的，客户在按下按键后1/5秒响应自己的事件。 这是相当不错的100毫秒滞后。 跨越延迟每个方向很容易超过200毫秒，拨号连接（很少见，但今天仍然存在）可能会有超过500毫秒的延迟峰值。 如果你在局域网或类似的东西上玩，这一切都不重要，但在互联网上，这种反应迟钝可能是无法忍受的。 
 
 这就是客户端预测（CSP）的概念所在.CSP被认为是大而可怕的，但是正确实施并且经过深思熟虑它实际上非常简单。 CSP的一个有趣特性是客户可以立即处理他们的输入 （客户端预测会发生什么）。 当然，客户可以（并且经常会）出错。 这意味着客户端需要一种从服务器应用更正的方法。 这意味着您需要一种方法让服务器验证，拒绝或修改来自客户端的RPC请求，以及一种序列化游戏状态的方法（因此可以将其恢复为从中重新模仿的基点）。 
 
 这样做有很多很好的资源。 我特别喜欢http://www.gabrielgambetta.com/?p=22 ，但你真的应该寻找一款好的多人游戏编程书。 
 
 
 即使在阅读了有关Flex和AS3的评论之后，我也必须建议socket.io。 易用（以及与节点的简单集成）使其成为我曾经使用过的基于HTTP的网络游戏的最佳（最佳？）选项之一。 我会进行必要的调整以便能够使用它。 我相信AIR / AS3至少有一个WebSockets库，即使socket.io本身不可用。 

To elaborate on driushkin's answer, you should use remote procedure calls (RPC) and an event queue. This works like in the image you've posted, where each packet represents a 'command' or RPC with some arguments (i.e. movement direction). You'll also need an event queue to make sure RPCs are executed in order and on time. This will require a timestamp or framecount for each command to be executed on (at some point in the future, in a simple scheme), and synchronized watches (World War II style).
 
You might notice one critical weakness in this scheme: RPC messages can be late (arrive after the time they should be applied) due to network latency, malicious users, etc. In a simple scheme, late RPCs are dropped. This is fine since all clients (even the originator!) wait for the server to send an RPC before acting (if the originating client didn't wait for the server message, his game state would be out of sync with the server, and your game would be broken).
 
Consider the impact of lag on such a scheme. Let's say the lag for Client A to the server was 100ms, and the return trip was also 100ms. This means that client input goes like:
 
 
 
Client A presses key, and sends RPC to server, but doesn't add it locally (0ms)
 
 
Server receives and rebroadcasts RPC (100ms)
 
 
Client A receives his own event, and now finally adds it to his event queue for processing (200ms)
 
 
As you can see, the client reacts to his own event 1/5 of a second after he presses the key. This is with fairly nice 100ms lag. Transoceanic lag can easily be over 200ms each way, and dialup connections (rare, but still existent today) can have lag spikes > 500ms. None of this matters if you're playing on a LAN or something similar, but on the internet this unresponsiveness could be unbearable.
 
This is where the notion of client side prediction (CSP) comes in. CSP is made out to be big and scary, but implemented correctly and thoughtfully it's actually very simple. The interesting feature of CSP is that clients can process their input immediately (the client predicts what will happen). Of course, the client can (and often will) be wrong. This means that the client will need a way of applying corrections from the Server. Which means you'll need a way for the server to validate, reject, or amend RPC requests from clients, as well as a way to serialize the gamestate (so it can be restored as a base point to resimulate from).
 
There are lots of good resources about doing this. I like http://www.gabrielgambetta.com/?p=22 in particular, but you should really look for a good multiplayer game programming book.
 
 
I also have to suggest socket.io, even after reading your comments regarding Flex and AS3. The ease of use (and simple integration with node) make it one of the best (the best?) option(s) for network gaming over HTTP that I've ever used. I'd make whatever adjustments necessary to be able to use it. I believe that AIR/AS3 has at least one WebSockets library, even if socket.io itself isn't available.