• 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: Even more DO problems
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Even more DO problems


  • Subject: Re: Even more DO problems
  • From: Sailor Quasar <email@hidden>
  • Date: Tue, 10 Jun 2003 00:46:23 -0400

On Monday, June 9, 2003, at 07:28 PM, Lloyd Dupont wrote:
it looks like your method is never ending (returning), is it ?

Debugging on both processes proves that:
1) The client's transmitData: method is blocked somewhere in the DO runtime, inside where it calls [proxyToServer sendData:data];
2) The server's sendData: method, which is the message called from the client, returns normally to the runloop of the server, which is in a detached thread. I have called NSConnection's enableMultipleThreads: method in both client and server.
3) The server succeeds in responding to other requests while the first client is blocked, and any further clients block in exactly the same place. It's as if the reply to the message is never sent or received, though without access to what DO is doing I can't be sure which. The message is -(void)sendData:(NSData *)data; If declared as -(oneway void)sendData:(NSData *)data;, all works fine. The problem is, I WANT the client to block until the server receives the message (or times out), which is what oneway is specifically designed not to do.

On Tuesday, June 10, 2003, at 06:02 AM, Sailor Quasar wrote:

Ok, I got a multithreaded client-server setup almost working with Distributed Objects, but there's a problem...

The client opens a connection to the server and sends some data across using a message for the purpose. If I declare the message as (oneway void), all is well with the world. If I don't use oneway, the client blocks forever somewhere inside the DO runtime. The server receives the message, and the relevant run loops are running on both sides. Any ideas what I might be doing wrong?

-- Sailor Quasar, guardian of Leraz's memory
"Face of stone, mind of calm, soul of love."
Email: email@hidden
_______________________________________________
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.



-- Sailor Quasar, guardian of Leraz's memory
"Face of stone, mind of calm, soul of love."
Email: email@hidden
_______________________________________________
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.

References: 
 >Re: Even more DO problems (From: Lloyd Dupont <email@hidden>)

  • Prev by Date: Re: PPP Control
  • Next by Date: Re: C question for you old guys ;-)
  • Previous by thread: Re: Even more DO problems
  • Next by thread: Re: Even more DO problems
  • Index(es):
    • Date
    • Thread