Changes between Version 1 and Version 2 of FutureRepyExceptions/PortInUseError

Changes between Version 1 and Version 2 of FutureRepyExceptions/PortInUseError

Please note that these Trac pages are no longer being updated. Wiki contents/documentation have moved to GitHub.

Changes between Version 1 and Version 2 of FutureRepyExceptions/PortInUseError

Please note that these Trac pages are no longer being updated. Wiki contents/documentation have moved to GitHub.

Changes between Version 1 and Version 2 of FutureRepyExceptions/PortInUseError

Show
Ignore:
Timestamp:
12/22/09 10:24:24 (10 years ago)
Author:
cemeyer
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • FutureRepyExceptions/PortInUseError

    v1 v2  
    1 In the FutureRepyExceptionHierarchy, PortInUseException is a network exception raised when another program is using a port that a repy program wants to bind to. It is distinguished from AddressBindingError in that it is expected to happen and user programs should handle it. I'm not sure if AddressBindingError should be a subclass of this, or vice versa, or if they should remain distinct. 
     1In the FutureRepyExceptionHierarchy, PortInUseException is a network exception raised when another program is using a port that a repy program wants to bind to. It is distinguished from AddressBindingError in that it is expected to happen and user programs should handle it. 
     2 
     3Conrad: I'm not sure if AddressBindingError should be a subclass of this, or vice versa, or if they should remain distinct.