• 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: Robust DO connections
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Robust DO connections


  • Subject: Re: Robust DO connections
  • From: Michael Latta <email@hidden>
  • Date: Fri, 4 Apr 2003 08:23:20 -0800

It has been quite a few years since I worked with DO, but as I recall the idea is to listen for new clients on a dedicated connection, then open private connections for each conversation. Each client conversation then can operate on its own thread. With all the clients sharing on e connection you are serializing all traffic to the server.

Michael Latta

On Thursday, April 3, 2003, at 03:58 AM, Terry Smyth wrote:

Hi,

I'm using DO to build a client server architecture into my application, using Rendezvous to select my server, and NSSocketPort to connect. Most aspects are now working really well (thanks to the many helpful posts on this list), and it is reasonably robust in most circumstances, provided that whichever end is closing down has a chance to notify the other end, so that things can be tidied up cleanly.

My issue at the moment is that if one of my clients suffers a catastrophic crash, the server is not notified. And worse still, the connection seems to be broken for all other clients (not good). I tried polling the clients to detect if they go "dead", but after one client dies, the server can't talk to any of them. Is this behavior expected? What is the latest recommended way to ensure DO works robustly. (I've got exception handlers around connection attempts, and message sending)

Is is possible (and would it help) to talk to each client on a new NSConnection (ie different from the listening connection) to reduce the possibility of one client affecting others?

I'm interested to hear if others are fully satisfied with the robustness of DO/NSConnection/NSSocketPort. ie does it survive client apps, or client machines crashing, cables unplugging etc?

Thanks,
Terry Smyth
Software Generation Limited
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.

  • Follow-Ups:
    • Re: Robust DO connections
      • From: Terry Smyth <email@hidden>
References: 
 >Robust DO connections (From: Terry Smyth <email@hidden>)

  • Prev by Date: Re: right way to load initial data in controls when opening a window
  • Next by Date: Extracting Safari's favicons cache
  • Previous by thread: Robust DO connections
  • Next by thread: Re: Robust DO connections
  • Index(es):
    • Date
    • Thread