1.0.0 version

[mcollina]

I am think about releasing a 1.0.0 version to stabilize each Ascoltatore API.
I think it is fairly stable right now.

What I would like to include:

• EE2Ascoltatore Ascoltatore using EventEmitter2. Comes out slower than TrieAscoltatore. #61.
• Single level wildcards Use '+' as single level wildcard to make it consistent with mqtt ascoltatore #62.
• remove newTopic Remove newTopic #60.
• remove while iterating Modifying _set while iterating #56.
• Define in the README the Ascoltatore API, mainly publish, subscribe and close.
• Define in the README the configuration options Better README #64.
• Code coverage Code Coverage with Instanbul #67.

[mcollina]

@davedoesdev have you got any other issue that you might want to get fixed in a 1.0.0 release?

I'd like to have #46, #54 and #51, but that seems too much.

[davedoesdev]

No I don't have any other issues. I think the whole clustering/bridge thing is too much for 1.0.0.
I was wondering also about whether topics could be sharded across mosca instances or something like that.

[mcollina]

Mosca and Ascoltatori already allows to use the same topic on two different instances, just use mongo, redis, or rabbit as a backend. Sharding them vertically is also already possible, but not in an automatic way.

[davedoesdev]

I think a v1.0.0 should have code coverage results available.

[mcollina]

Seems fair.
It should be pretty hight, but it is better to verify it.

I plan to give a go with instanbul.