Split out connection details from gubbins.

[midijohnny]

The 'connnection' details are designed for user configuration (i.e. what server to connect etc).
The 'logentry' are 'internal' to the App.
It would be useful therefore to be able to externalise 'connection' details in a file 'config.xml' - but without the other stuff being present.

Probably - use either bindings to re-introduce the other details into the default model - that keeps the xpath simpler, without having to reach explicitly to other instances. (or just use bind ids in the UI?)