Event streams behave differently if query string is present

[kyork-cl]

This isn't documented in the wiki, but it seems that you can open the events stream with a "topic" parameter like wscat -c ws://localhost:1337/events?topic="**". This seems to work as you would expect in that events matching the topic value are received with two exceptions:

1. The socket does not respond to subscription events as outlined in the documentation
2. Event data received doesn't match the format outlined in the documentation, it seems to follow the format for a direct connection to a monitored value (eg the "topic" doesn't contain the server ID)

What is the expected behavior for this usage?

[AdamMagaluk]

This is expected behavior and we probably need better documentation on the differences.

When we started the multiplexed ws feature we made the decision to make the existing streams backwards compatible with older versions of zetta. This means no subscription acks and old formating.

Regarding 2, this poses issues with not being able to identifying the originating server, previously you could not subscribe to wildcards that match multiple servers.