If we connect to a secure server we should return tls:// as prefix even if not specified in Connect() call.

//cc @thejameskyle @cmaher

Hello,

I am hosting both client and WampHost in ASP.NET Core application. Was trying to use WampChannelReconnector to enable reconnection, but when I stop my WampHost application reconnection not always happening. Sometimes it is happening, but as I stop/start my host at some point it stops, or might not be triggered even once.

From the logs I am getting this error in my client application:

Currently, After we create a partitioned topic, for a topic that has no producer/consumer created on it,
running command
bin/kafka-run-class.sh kafka.tools.GetOffsetShell --broker-list 127.0.0.1:9092 --topic topic8 --time -1
will return
"Topic topic8 does not exist".

The Extensions.Logging has become the standard for .NET as an logging abstraction. We should use it instead of the older Common.Logging.

Currently, query parameter values are kept on navigation since they could be relevant to the target, and individual widgets should not be concerned with collecting/keeping parameters that are not relevant for themselves.

However, sometimes this means that query parameters start accumulating, and are kept on pages where they have no meaning. It should be possible to determine a set of "relevan

• edit/revise the README to reflect the actual public interface
• be sure to document all configuration options (create a wiki page if needed)
• Write doc comments for all public classes, methods, constants, etc.
• Add chasqui to rubydoc.info
• update the examples to reflect the actual public interface https://github.com/jbgo/chasqui/tree/master/examples