• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: CFSocket freezes
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: CFSocket freezes


  • Subject: Re: CFSocket freezes
  • From: jkp <email@hidden>
  • Date: Sun, 27 Nov 2005 09:25:05 +0000

Im also interested in the use of xinetd or launchd to handle multiple connections to a server. The issue I would have is that all the server instances would need to communicate, ideally as threads within the same process. I cant see a way to adapt this pattern to get a "singleton" server process to spawn new threads....is such a thing possible?

Jamie

On 27 Nov 2005, at 09:19, Greg Herlihy wrote:

Servers generally do not implement a GUI interface themselves, because they
have no need of one. A server's clients are remote, and are therefore not
able to interact with the server using its keyboard, mouse and monitor as
they would were they using a desktop application. Instead all communication
between the server and its users, is electronic, and therefore, faceless.


And certainly in the interests of stability, performance and security, the
only code that the server should be executing, is code needed to service its
clients. All other nonessential functions, such as presenting a GUI (even
for an administrator) should be handled by a separate application, and
ideally one running on a different machine than the server's.


In practice, a GUI interface for a server (if one exists) is invariably some
kind of a client application - sometimes just a web browser - that can
monitor and send commands to the server as it is running. And, one again to
maximize the server's performance and to safeguard its stability, this GUI
client app should run on its own machine and communicate to the server over
the network, as a client.


So to answer your question: it's highly unlikely that any online game server
incorporates a GUI directly, for the reasons outlined above. And if one in
fact turned out to exist, it would make a lot of sense to move its GUI out
of the server, again for the same reasons. The ideal server app is minimal,
efficient and simple - while a typical GUI implementation has none of those
characteristics.


Greg


On 11/26/05 4:02 PM, "Markus Hitter" <email@hidden> wrote:


Am 27.11.2005 um 00:50 schrieb Greg Herlihy:

In fact it is hard to think of any disadvantages with this [launchd
service] approach.

How would you implement a server with a GUI, e.g. an online game, using a launchd service?


Markus

- - - - - - - - - - - - - - - - - - -
Dipl. Ing. Markus Hitter
http://www.jump-ing.de/






_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40kirkconsulting.co.uk


This email sent to email@hidden

_______________________________________________ Do not post admin requests to the list. They will be ignored. Cocoa-dev mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden
References: 
 >Re: CFSocket freezes (From: Greg Herlihy <email@hidden>)

  • Prev by Date: Re: CFSocket freezes
  • Next by Date: Re: CFSocket freezes
  • Previous by thread: Re: CFSocket freezes
  • Next by thread: Re: CFSocket freezes
  • Index(es):
    • Date
    • Thread