Re-arrange the example code to show the intent in a clearer manner.

While the example code is functional, it doesn't highlight the
dependencies between the lines as best it could.  The rearranged code
adds comments to help explain that producers write to 'addresses', that
'queues' are bound to an address and that client's read from a 'queue'.

Explaining this separation clearly is needed in order to understand
how to turn this example into a publish/subscribe model.
Transfer queue tool
Merge pull request #1699 from clebertsuconic/upmaster

Transfer queue tool
HORNETQ-1367 - Allow QueueControlImpl.removeMessage(long) to operate on scheduled messages
Merge pull request #1705 from jbertram/master

HORNETQ-1367 - Allow QueueControlImpl.removeMessage(long) to operate on ...
adding filter to TransferQueue

adding user/password / few tweaks on transfer tool
Merge pull request #1698 from gkopff/doc_8_2_a_simple_example

Re-arrange the example code to show the intent in a clearer manner.
added scale down management method
Merge pull request #1704 from clebertsuconic/upmaster

adding filter to TransferQueue
Merge pull request #1700 from andytaylor/master

added scale down management method
AMQP Multi Protocol support
Renaming ProtonRemotingconnection
simple renaming
more work done
more work
work done
work
fix
more work
fix