Ravi Shankar

Hey everyone! I've been working on OpenAPI-related tooling over the past few weeks - I'm not completely sure whether actix-web should stick to some specification such as OpenAPI v2/v3, so...

@fafhrd91 That'd be great! Thank you! I think I'll have a working version by this weekend. I'll post my updates here :)

0Hi @fafhrd91! Would it be possible to expose `Factory` and `AsyncFactory` traits? (through `dev` module at least?). It's internal atm, but in order to wrap all struct methods, I need...

Hello everyone! I've just released paperclip 0.3.0 and it comes with the initial version of actix-web plugin for hosting OpenAPI v2 spec. It shouldn't break your actix-web flow. Please try...

@Pzixel In the upcoming release (0.4.0), I'm focusing on getting v2 polished (because that's used by majority of the web). In the next release, I'll be focusing on v3. It's...

> The other crate supports it simply for the reason that the TLS implementation is based on OpenSSL and it is kinda broken, especially if your local libssl is old...

It turned out that this has got to do with NATS protocol itself **and** how nitox currently deals with TLS. When I tried debugging this with `openssl`, I got: ```...

Oh, and one minor thing that struck me - Nitox is [parsing the URL](https://github.com/YellowInnovation/nitox/blob/fae8a993a94f94b18a10e24aee3d42c9c2f42f6c/src/client.rs#L206) to get the host name when TLS is enabled. But, the [previous step](https://github.com/YellowInnovation/nitox/blob/fae8a993a94f94b18a10e24aee3d42c9c2f42f6c/src/client.rs#L193-L200) tries to parse...

> About the SocketAddr / Url business, I'll check it out, but the convention in NATS is to give something like nats://myserver.my.tld:port, or simply xxx.xxx.xxx.xxx:port. It doesn't seem weird either....

I have opened a PR for this!