Remove hosts resource #42

hosts as top level resource does not make much sense, but only pollutes URL. This is due to REST API implementation does not know any Tango host in advance and can not discover them in a simple way.

The better approach seems to be is to define devices, atrtibutes, commands and pipes as top level resource:

GET /devices?host={host[:port]}&domain={name/wildcard}&family={name/wildcard}&member={name/wildcard}

GET /devices/tree?host={host[:port]}&domain={name/wildcard}&family={name/wildcard}&member={name/wildcard}

GET /attributes?host={host[:port]}&domain={name/wildcard}&family={name/wildcard}&member={name/wildcard}&name={name}

e.g.

GET /attributes/value?host=localhost&host=hzgxenvtest&domain=sys&family=*&member=*&name=State&name=Status

will response value of State and Status attributes of all devices in sys domain of localhost:10000 and hzgxenvtest:10000 tango hosts.