make nats.Conn as an interface about nats.go

[derekcollison]

What type of wrapping are you trying to do? Why would not embedding a nats.Conn or a nats.EncodedConn work in this instance similar to how I have done it? I agree though they should be an interface.

[hsinhoyeh]

At the beginning, I want to wrap nats.Conn and make some stats on it.
And then I found that you have provided Stats in nats.Conn, so I can temporarily use it for now.
For a long term consideration, I still want to have such interface which makes the wrap easier.
How do you think?

[derekcollison]

It is definitely something I am considering, thanks for the feedback. Let
me know if Stats does not provide you what you need.

On Mon, Jun 16, 2014 at 10:33 AM, hsinhoyeh [email protected]
wrote:

At the beginning, I want to wrap nats.Conn and make some stats on it.
And then I found that you have provided Stats in nats.Conn, so I can
temporarily use it for now.
For a long term consideration, I still want to have such interface which
makes the wrap easier.
How do you think?

—
Reply to this email directly or view it on GitHub
#21 (comment).