When a node restarts it starts over again with fetching the configuration
-  It is not sure that it can use the "old dynamically allocated port number" again.
-  It should however try to reuse the old one, if not possible it should
allocate a new one. One has to be able to distinguish between portnumbers
specified originally in the config, and ones that has been dynamically added
(the latter may be changed if "busy", but the first cannot be changed).

We use negative portnumbers for ports that are ok to change.

into mysql.com:/home/stewart/Documents/MySQL/5.0/ndb-dynamic-ports-impl3

  forgot hex prefix

  improved printout routine

+ some more docs on event

+ some docs update on events

and removed usage of Ndb::waitUntilReady()

and provided some backwards compat functions

into mysql.com:/usr/local/home/marty/MySQL/mysql-5.0-ndb

+ some extra docs on the area
updated docs by removing som async stuff

and updated some docs

into poseidon.ndb.mysql.com:/home/tomas/mysql-5.0-ndb

into mysql.com:/home/stewart/Documents/MySQL/5.0/ndb-dynamic-ports-impl3

- Change configuration handling so that no default ports are given, but instead 0 is set (port to be dynamic)
- TransporterRegistry::start_service now only tries to connect when fetched port number > 0

into mysql.com:/home/jonas/src/mysql-5.0-ndb

into mysql.com:/home/jonas/src/mysql-5.0

into intelp4d.mysql.com:/users/vtkachenko/bk/mysql-5.0

  Fix Bug#7624

into sanja.is.com.ua:/home/bell/mysql/bk/work-5.0

into mysql.com:/home/jonas/src/mysql-5.0

into mysql.com:/home/jonas/src/mysql-5.0