blocks|key|4426215|text|当服务器将更新发送到客户端时，让一个线程处理所有更新可能会更容易，并且只使用异步套接字。当然，这也取决于你要处理多少个客户。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4426216|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

When the server sends updates to the clients, it would probably be easier to just have one thread handle them all, and just use async sockets. Of course this would depend on how many clients you had to deal with too.

blocks|key|4426261|text|只要客户端和服务器都是OS+X应用程序，并且都可以使用Cocoa框架用Objective-C编写，我强烈建议您看看Cocoa中的Distributed+Objects+(DO)技术。我不会尝试在这里给出分布式对象的教程，只是解释为什么它可能是有用的……|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|4426262|DO为你处理异步网络细节(你所有的客户端更新都可以在一个线程上进行)。此外，与远程对象通信的语义(客户端到服务器或相反；一旦建立连接，DO就是双向的)与进程内通信非常相似。换句话说，一旦您有了对远程对象的引用(实际上是充当连接另一端对象的代理的NSDistantObject+)，您的客户端代码就可以将消息发送到远程对象，就像它是本地对象一样：|style|CODE|4426263|[remoteServer+update:client];|code-block|syntax|javascript|4426264|从客户端或|4426265|[[remoteClientList+objectAtIndex:i]+update:server];|4426266|从服务器。在阅读完Distributed+Objects+programming+guide之后，我将把设置连接和获取remoteServer或remoteClient参考的细节留给您。|4426267|使用DO的缺点是您与Cocoa捆绑在一起；编写使用Distirbuted对象通信的非Cocoa客户机或服务器将非常困难。如果您可能想要使用非Cocoa客户端或服务器实现，则不应该使用DO。在这种情况下，我会推荐一些简单的，有很多跨平台和语言支持的东西。基于HTTP的REST风格的API是一个很好的选择。有关如何实现URL+Loading+System请求和响应的信息，请参阅Cocoa文档。查看苹果的CocoaHTTPServer示例代码或same+name的code.google.com项目，以获取有关在Cocoa代码中实现HTTP服务器的信息。|4426268|作为最后一种选择，如果您想实现自己的网络协议，可以查看Cocoa+Stream+Programming+Guide。NSStream的子类可以让你监听网络套接字，并处理对该套接字的异步读写。很多人使用AsyncSocket来实现这一目的。它包装了(低级的)+CFStream和CFSocket，使编写网络代码变得更容易。|4426269|entityMap|0|LINK|mutability|MUTABLE|url|http://developer.apple.com/DOCUMENTATION/Cocoa/Conceptual/DistrObjects/DistrObjects.html|1|2|http://developer.apple.com/DOCUMENTATION/Cocoa/Conceptual/URLLoadingSystem/Tasks/UsingNSURLConnection.html#//apple_ref/doc/uid/20001836|3|http://developer.apple.com/samplecode/CocoaHTTPServer/index.html|4|http://code.google.com/p/cocoahttpserver/|5|http://developer.apple.com/DOCUMENTATION/Cocoa/Conceptual/Streams/Streams.html|6|http://code.google.com/p/cocoaasyncsocket/^0|1S|J|0|0|3E|F|0|0|0|0|9|11|1|0|4E|I|2|5L|F|3|65|9|4|0|1M|8|X|O|5|2S|B|6|0^^$0|@$1|2|3|4|5|6|7|1F|8|@]|9|@$A|1G|B|1H|1|1I]]|C|$]]|$1|D|3|E|5|6|7|1J|8|@$A|1K|B|1L|F|G]]|9|@]|C|$]]|$1|H|3|I|5|J|7|1M|8|@]|9|@]|C|$K|L]]|$1|M|3|N|5|6|7|1N|8|@]|9|@]|C|$]]|$1|O|3|P|5|J|7|1O|8|@]|9|@]|C|$K|L]]|$1|Q|3|R|5|6|7|1P|8|@]|9|@$A|1Q|B|1R|1|1S]]|C|$]]|$1|S|3|T|5|6|7|1T|8|@]|9|@$A|1U|B|1V|1|1W]|$A|1X|B|1Y|1|1Z]|$A|20|B|21|1|22]]|C|$]]|$1|U|3|V|5|6|7|23|8|@$A|24|B|25|F|G]]|9|@$A|26|B|27|1|28]|$A|29|B|2A|1|2B]]|C|$]]|$1|W|3|-4|5|6|7|2C|8|@]|9|@]|C|$]]]|X|$Y|$5|Z|10|11|C|$12|13]]|14|$5|Z|10|11|C|$12|13]]|15|$5|Z|10|11|C|$12|16]]|17|$5|Z|10|11|C|$12|18]]|19|$5|Z|10|11|C|$12|1A]]|1B|$5|Z|10|11|C|$12|1C]]|1D|$5|Z|10|11|C|$12|1E]]]]

As long as both client and server are OS X apps and can both be written in Objective-C using the Cocoa frameworks, I would highly recommend you take a look at the <a href="http://developer.apple.com/DOCUMENTATION/Cocoa/Conceptual/DistrObjects/DistrObjects.html" rel="noreferrer">Distributed Objects</a> (DO) technology in Cocoa. I won't try to give a tutorial in Distributed Objects here, just explain why it might be useful...

DO handles asynchronous network details for you (all your client updates could happen on a single thread). In addition the semantics of communication with a remote object (client to server or visa versa; DO is bidirectional once the connection is established) are very similar to in-process communication. In other words, once you have a reference to the remote object (really an <code>NSDistantObject</code> which acts as a proxy to the object on the other end of the connection), your client code can send messages to the remote object as if it were local:

<pre><code>[remoteServer update:client];
</code></pre>

from the client or

<pre><code>[[remoteClientList objectAtIndex:i] update:server];
</code></pre>

from the server. I'll leave the details of setting up the connection and for getting the remoteServer or remoteClient reference to you after reading the <a href="http://developer.apple.com/DOCUMENTATION/Cocoa/Conceptual/DistrObjects/DistrObjects.html" rel="noreferrer">Distributed Objects programming guide</a>.

The downside of using DO is that you are tied to Cocoa; it will be very difficult to write a non-Cocoa client or server that communicates using Distirbuted Objects. If there's a chance you may want to have non-Cocoa client or server implementations, you should not use DO. In this case, I would recommend something simple with a lot of cross-platform and language support. A REST-style API over HTTP is a good option. Have a look at the Cocoa <a href="http://developer.apple.com/DOCUMENTATION/Cocoa/Conceptual/URLLoadingSystem/Tasks/UsingNSURLConnection.html#//apple_ref/doc/uid/20001836" rel="noreferrer">URL Loading System</a> documentation for info on how to implement HTTP requests and responses. Have a look at Apple's <a href="http://developer.apple.com/samplecode/CocoaHTTPServer/index.html" rel="noreferrer">CocoaHTTPServer</a> example code or a code.google.com project of the <a href="http://code.google.com/p/cocoahttpserver/" rel="noreferrer">same name</a> for info on implementing an HTTP server in your Cocoa code.

As a very last option, you can take a look at the Cocoa <a href="http://developer.apple.com/DOCUMENTATION/Cocoa/Conceptual/Streams/Streams.html" rel="noreferrer">Stream Programming Guide</a> if you want to implement your own network protocol. <code>NSStream</code>'s subclasses will let you listen on a network socket and handle asynchronous reads/writes to/from that socket. A lot of people use <a href="http://code.google.com/p/cocoaasyncsocket/" rel="noreferrer">AsyncSocket</a> for this purpose. It wraps the (lower-level) CFStream and CFSocket and makes writing network code somewhat easier.

blocks|key|361915|text|我不知道您计划如何设计您的系统，但通常服务器不能连接到客户端；客户端必须启动通信。对于50个客户端的低限制，您可能不会考虑类似web服务器/客户端的实现……|type|unstyled|depth|inlineStyleRanges|entityRanges|data|361916|也就是说，基本上有两种方法来处理客户端服务器通信:+1.客户端定期轮询服务器以获取更新2.客户端保持到服务器的连接是开放的，服务器使用众所周知的(两端都理解的)协议进行响应。|361917|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I don't know how you plan to design you system, but usually a server cannot connect to a client; the client must initiate the communication. With a low limit of 50 clients, you may not be looking at a web-server/client-like implementation...

That said, there are basically two ways to handle client server communication:
1. The client polls the server periodically to get updates
2. The client keeps a connection open to the server and the the server responds with a well known (as in both sides understand it) protocol.

blocks|key|1048756|text|在苹果开发者方面，有几个网络方面的例子。我建议你去看看URLCache，它可以下载。引用本例的Apple文档：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1048757|1048758|+URLCache是一个示例iPhone应用程序，它演示了如何从web上下载资源，将其存储在应用程序的数据目录中，以及如何使用资源的本地副本。URLCache还演示了如何实现两个缓存策略：|blockquote|1048759|1048760|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|J|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|K|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|L|8|@]|9|@]|A|$]]|$1|G|3|-4|5|6|7|M|8|@]|9|@]|A|$]]]|H|$]]

There's several networking examples in the apple developer side.
One I would recommend that you check out is the URLCache, which can be downloaded.
Quoting from the Apple's documentation for this example:

<blockquote>
 URLCache is a sample iPhone application that demonstrates how to download a resource off the web, store it in the application's data directory, and use the local copy of the resource. URLCache also demonstrates how to implement a couple of caching policies:
</blockquote>

blocks|key|362011|text|一个有趣的选择是来自Jens+Alfke的BLIP协议。它就像是BEEP的精简版:面向消息的网络系统。它基本上提供了双向消息管道的低级抽象，因此您可以专注于在其上分层通信协议。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|362012|它有一些值得关注的追随者，比如CoreData圣经的作者Marcus+Zarra和飞肉软件的Gus+Mueller。|362013|entityMap|0|LINK|mutability|MUTABLE|url|http://jens.mooseyard.com/|1|http://bitbucket.org/snej/mynetwork/wiki/Home|2|http://en.wikipedia.org/wiki/BEEP|3|http://github.com/mzarra^0|A|A|0|L|4|1|W|4|2|0|S|C|3|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@$A|U|B|V|1|W]|$A|X|B|Y|1|Z]|$A|10|B|11|1|12]]|C|$]]|$1|D|3|E|5|6|7|13|8|@]|9|@$A|14|B|15|1|16]]|C|$]]|$1|F|3|-4|5|6|7|17|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]|N|$5|I|J|K|C|$L|O]]|P|$5|I|J|K|C|$L|Q]]|R|$5|I|J|K|C|$L|S]]]]

An interesting option is the <a href="http://bitbucket.org/snej/mynetwork/wiki/Home" rel="nofollow noreferrer">BLIP</a> protocol from <a href="http://jens.mooseyard.com/" rel="nofollow noreferrer">Jens Alfke</a>. It's like a stripped down version of <a href="http://en.wikipedia.org/wiki/BEEP" rel="nofollow noreferrer">BEEP</a>: a message oriented networking system. It basically provides the low-level abstractions for a bidirectional message pipe so you can concentrate on layering your communication protocol on top of it. 

It has some worthy followers such as <a href="http://github.com/mzarra" rel="nofollow noreferrer">Marcus Zarra</a> (author of the CoreData bible) and Gus Mueller of Flying Meat software.

I'm building an Objective-C app that has both a server and a client. The client can send updates to the server, and the server needs to be able to send updates to each connected client. I've been thinking about how best to implement this system, but am asking for your suggestions.

Currently, I'm thinking that when new updates are available, the server will use threads to send the update to each client in turn. If a client times out, they are disconnected.
I have very little networking experience, so am asking your insight.

Do you think that this system would work well?
If so, do you have any suggestions about how to do the threading? Any NS classes you can point me at? There's got to be some kind of queue I can use, I'm thinking.

Any other thoughts?

EDIT: I do not expect the client count to get much above 50 or so, at the max.

Objective-C networking - best practices?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我正在构建一个同时具有服务器和客户端的Objective-C应用程序。客户端可以向服务器发送更新，服务器需要能够向每个连接的客户端发送更新。我一直在思考如何最好地实现这个系统，但我在征求您的建议。目前，我认为当有新的更新可用时，服务器将使用线程依次将更新发送到每个客户端。如果客户端超时，它们将断开连接。我只有很少的网络...

问Objective-C网络-最佳实践？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Objective-C网络-最佳实践？EN