[macrophyllum]

Hi,

I have a networking application that uses distributed objects (DO) for communication between the server and client. The server pings the client every once in a while to make sure that it is still there. I am running into a problem where if the client has a modal sheet down and the ping occurs, the client does not respond and the server ends up thinking the client is no longer there.

So my question is: do you think I should have my connections happen in a different thread, or before the client beings a modal sheet should it tell the server that it is in a modal state. Or, is there a better alternative all together?

Feedback appreciated.
~Ian

[smeger]

I'd say to use a separate thread. It's not particularly tough to do, and it'll get around the problem nicely.

If you have any variables that are shared between your new thread and the main thread, make absolutely sure to lock a shared NSLock before you access them. And don't do UI stuff from your new thread - if you need to, message the main thread and have it done there.

[Chuckit]

You could have the connection listen in more than just NSDefaultRunLoopMode (for example, kCFRunLoopCommonModes). That seems like the simplest way to do it.

[macrophyllum]

I tried this and it worked:

[NSApp beginSheet....


[NSApp abortModal];

This allows the sheet to come down and everything looks and works fine, but we are not in a modal session so my client still receives messages from the server. Or at least that is what I think is going on