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

DO Connections


  • Subject: DO Connections
  • From: Anthony Duer <email@hidden>
  • Date: Tue, 29 Oct 2002 17:34:38 -0800

I think I've found the reason why a NSThread that listens on a socket using a simple while loop is causing drawing problems. I thought posting a NSNotification would have that data safely exit the secondary thread to a thread where it's safe to draw to the screen from. Apparently not. Thus, I've decided to move my NSThread into a separate class and have a DO connection link back to main thread. However, the main stickler is this: If the separate class running my second NSThread is locked into a continuous while loop, how can the main thread inform the secondary thread that the socket is supposed to close? Is there a way to share a memory address for a BOOL and safely have both threads access it?

~Anthony Duer
_______________________________________________
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: DO Connections
      • From: Douglas Davidson <email@hidden>
  • Prev by Date: XML-/HTML-safe formatted output from NSString
  • Next by Date: Re: XML-/HTML-safe formatted output from NSString
  • Previous by thread: Re: XML-/HTML-safe formatted output from NSString
  • Next by thread: Re: DO Connections
  • Index(es):
    • Date
    • Thread