Distirbuted Objects error handling?
Distirbuted Objects error handling?
- Subject: Distirbuted Objects error handling?
- From: "Rafael K. Kobylinski" <email@hidden>
- Date: Thu, 28 Feb 2002 18:18:38 +0100
Hello,
I am using Distributed Objects with NSSocketPort for a
NotificationCenter kind of server application, where clients can
attach and will be notified if interesting events occur.
The communication works, but I would like to make it more robust and
therfore catch as many network related errors as possible.
I read the documentation and searched the list, but was not able to
find any method to find out if the listening port I create with
[[NSConnection alloc] initWithReceivePort:receivePort sendPort:nil]
is really created or fails immediately because the port is in use. Is
there a way to check this?
Another problem is on the client side, where I do register for
NSConnectionDidDieNotification but I am not notified if the server
crashes (I know that on the TCP level there is no way to find that
out unless you check the connection periodically). Actually it's the
same on the server side. Is this the correct behaviour?
I have written exception handlers to catch NSPortTimeoutException
around messages to remote objects. What else should I do? Are there
any examples on using Distributed Objects which would include full
error handling the "right" way?
--
Rafael K. Kobylinski Email: email@hidden
Institut f|r Informatik Tel. : ++ 49 89 289 22391
Technische Universitdt M|nchen Cell.: ++ 49 177 7 495020
_______________________________________________
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.