






UC5.2b Alternative ODIN peer that does not use Hostcatcher
The user may use an ODIN peer that is not the sample randomwalkpeer supplied with the ODIN toolkit. This ODIN peer conceivably might not make use of a hostcatcher - at least not a single, static one for whole overlay network.
Actors: See Parent Use Case.
Stakeholders and Interests: See Parent Use Case.
Preconditions:
The parent preconditions still holds except for these items:
- There is a property file for each instance of randomwalkpeer, detailing the ODIN hostcatcher's IP address and port, peer logic type (e.g. RandomWalkPeer Logic) and topology manager type (e.g. SquareRootTopologyManager). One property file could be shared across all instances. The hostcatcher's IP address and port should be consistent across property files.
- There are index files for each instance of randomwalkpeer except the hostcatcher. Using the same index file for all instances is probably not desired.
If the user uses an alternative ODIN peer, it may not require the user to supply property files or index files. It may require alternative or additional files. This alternative ODIN peer would either be developed by the user, or its requirements and usage would be documented elsewhere. While our software will support all peers that use the ODIN library, we can not anticipate the requirements of all peers.
Also all mentions of a hostcatcher are invalidated.
Success Guarantee (Postconditions): See Parent Use Case.
Main Success Scenario
The parent success scenario still holds except for these items:
- User configures property files and index files to their liking for each ODIN instance.
There may be alternative or additional files to configure.
- User starts the ODIN hostcatcher instance first. This instance should be started with log level 3 (the minimum level for visualization) or higher, and log output should be directed to a unique file in the directory created above.
- User terminates the hostcatcher last.
If there is no hostcatcher, there do not have to be particular instructions for them.
Extensions (Alternative Flows):
NONE
Special Requirements:
NONE
Technology and Data Variation List: See Parent Use Case.
Frequency of Occurrence: See Parent Use Case.
Open Issues:
None
Links to this Page