Daemonize sending

[thomax]

Also refactor the handling of pebblebed connectors.

[atombender]

Why not just use Hermes::Configuration.instance whenever you want the config?

[thomax]

Just because it's shorter :)

[thomax]

@atombender Are we good to go? This branch won't cause problems for any of your Hermes clients?

[atombender]

I agree this is a potential hazard, but wouldn't this be a design flaw under which all our apps using queue listeners suffer? How could we reliably subscribe only to data changes which where initiated by a specific pebble?

I don't know about your apps, but that's a design flaw one should avoid and which is easily avoided by carefully using the appropriate events that represent intent. For example, the Hermes API, after creating a Grove document, could post an event hermes.send_message which Hermes' listener then listens to. There's no need to listen to Grove changes (which could blow up and result in sending circumventing the Hermes API) that way.

Other than that, I think your changes are fine.