Issue 277:  Destroying an iteratorr (naming)
Source:  (, )
Nature:  Uncategorized
Severity: 
Summary: Summary: Naming Service implementation should be free to destroy an iterator as soon as last value has been retrieved. Clients should be allowed to call next_one or next_n after one of these calls.

Resolution: 
Revised Text: 
Actions taken:
October 18, 1996: received issue
Discussion: 

End of Annotations:=====