Re: sending over DO seems to make main process block?
- From: noreply@xxxxxxxxxxxx (Patrick Machielse)
- Date: Sun, 13 May 2007 11:58:38 +0200
Wizumwalt@xxxxxxxxx <Wizumwalt@xxxxxxxxx> wrote:
[NSConcretePortCoder dispatch]
<dyld_stub_objc_exception_throw>
Two things come to mind:
1) DO is one of the few places in Cocoa where exceptions are thrown that
are worth catching. For instance, an exception may be thrown when the
connection times out. Use code like this:
@try {
// try to send message over DO
@catch (NSException *e) {
NSLog(@"%@", [e localizedDescription]);
// handle connection failure here
}
2) When designing your DO communication scheme, you must take care to
avoid deadlock. For instance, if after sending a oneway void message,
the sender expects to be called back from the receiver, it (the sender)
should not be stuck in a blocking call somewhere... When you are using
DO within 1 application the potential for deadlock seems greater.
patrick
.
- References:
- sending over DO seems to make main process block?
- From: Wizumwalt@xxxxxxxxx
- Re: sending over DO seems to make main process block?
- From: Patrick Machielse
- Re: sending over DO seems to make main process block?
- From: Wizumwalt@xxxxxxxxx
- Re: sending over DO seems to make main process block?
- From: Wizumwalt@xxxxxxxxx
- Re: sending over DO seems to make main process block?
- From: Patrick Machielse
- Re: sending over DO seems to make main process block?
- From: Wizumwalt@xxxxxxxxx
- sending over DO seems to make main process block?
- Prev by Date: resizing windows programatically
- Next by Date: Re: there has to be a better way than this
- Previous by thread: Re: sending over DO seems to make main process block?
- Next by thread: Re: sending over DO seems to make main process block?
- Index(es):
Relevant Pages
|