#57 Allow persistence of address-hosting peers

[Neil Avery]

When providing a set of known hosts address lists will
be accumulated on contact with each peer. Well-known
address hosting peers should be queried first, but
should also persist address information.

[Neil Avery]

Logged In: YES
user_id=922728

Super-node information should be kept for the binding
service to bind to. It should persist the peer list and
classification of each node in an organised list. (XML
persistable treelist). The peer list is scanned when the
bindingservice starts up binding to super-node addressses
first. maybe add on !super-node to the URI and allow for it
on the hashcode function sorting.

introduce: SortablePeerList(URI self)
->add(URI peer)
->iterator()
->remote(URI peer)