Issue 3106: Default values for to_url are problematic                                                                                                                                                               (naming_ftf)
Source: DSTC (Mr. Ted McFadden, mcfadden@dstc.edu.au)
Nature: Uncategorized Issue
Severity: 
Summary: Summary: In the operation to_url, defaulting the address and protocol for
to iiop and localhost is of little value and has created some confusion.
Suggest that no default be allowed
Resolution:  Agreed.
Revised Text: Change end of last paragraph describing to_url operation description on page 3-22 to read: " It is legal for the
stringified name to be emtpy. If the address is empty, an InvalidAddress exception is raised."
Actions taken:
December 10, 1999: received issue
May 4, 2000: closed issue
Discussion: 

End of Annotations:=====
X-Authentication-Warning: errigal.ooc.com.au: tmcf owned process doing
-bs
Date: Fri, 10 Dec 1999 15:56:46 +1000 (EST)
From: Ted McFadden <tmcf@ooc.com.au>
To: issues@omg.org
Subject: 2 Naming Issues need formal numbers
Message-ID:
<Pine.LNX.4.10.9912101551550.2835-100000@errigal.ooc.com.au>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-UIDL: "Ak!!)3\d96dR!!`Af!!

Hi,

These 2 items have grown into issues in the naming FTF
and are being voted on as such, can we have formal
numbers assigned to them?

Thanks,
Ted.
==========Unassigned Issues Under Discussion===============

Issue NN-0001: Default values for to_url are problematic
Source: naming_ftf discussion list 
Nature: 
Severity: 
Summary: In the operation to_url, defaulting the address and protocol
for
to iiop and localhost is of little value and has created some
confusion.
Suggest that no default be allowed