bugGNUstep - Bugs: bug #3984, NSConnection registration with...

 
 

You are not allowed to post comments on this tracker with your current authentication level.

bug #3984: NSConnection registration with same name should not raise exception

Submitted by:  Stefan Urbanek <stefanu>
Submitted on:  Sat 14 Jun 2003 07:47:34 PM UTC  
 
Category: Base/FoundationSeverity: 1 - Wish
Item Group: BugStatus: None
Privacy: PublicAssigned to: Richard Frith-Macdonald <CaS>
Open/Closed: Closed

Fri 25 Jul 2003 04:13:19 PM UTC, comment #1:

Fixed in CVS

Richard Frith-Macdonald <CaS>
Project MemberIn charge of this item.
Sat 14 Jun 2003 07:47:34 PM UTC, original submission:

If I use [conn registerName:someName] and someName is already registered i get an exception. The registerName: method should return NO on unsuccessfull registration. Apple docs for registerName says:

--
Registers the receiver with the default NSPortNameServer under name on the local host, returning YES if successful, NO if not (for example, if another NSConnection on the same host is already registered under name).
--

It is more logical NOT to raise an exception, for example if i want to register objects with similar name with a sequence number.

Stefan Urbanek <stefanu>
Project Member

 

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

CC list is empty

 

Do you think this task is very important?
If so, you can click here to add your encouragement to it.
This task has 0 encouragements so far.

Only logged-in users can vote.

 

Please enter the title of George Orwell's famous dystopian book (it's a date):

 

 

Follow 4 latest changes.

Date Changed By Updated Field Previous Value => Replaced By
Fri 25 Jul 2003 04:13:19 PM UTCCaSOpen/ClosedAnalyzed=>(Error - Not Found)
Fri 04 Jul 2003 05:44:05 AM UTCCaSSeverity3 - Normal=>(Error - Not Found)
  Assigned toNone=>NA
  Open/ClosedOpen=>(Error - Not Found)

Back to the top


Powered by Savane 3.1-cleanup1