Implements Send trait on Connection.

[ArtBlnd]

It is very hard to use neqo-transport crate with other async crates such as tokio, async-std.
those crate requires Send traits to spawn tasks.

currently, some Rc objects causes Connection to be !Send.

maybe related to #530

[agrover]

Hmm. If you want to experiment with this, replacing instances of Rc with Arc and RefCell with Mutex would probably be the first place to start making changes. The next issue you'd hit would probably be something nss related.

Happy hacking!

[martinthomson]

The design relies heavily on thread confinement, so care would be needed to ensure that connections can't be accessed from multiple threads.

[ArtBlnd]

The design relies heavily on thread confinement, so care would be needed to ensure that connections can't be accessed from multiple threads.

I didn't meant to support Sync so its fine :)

[ArtBlnd]

Seems unsafely implementing Send traits looks fine if its bounded with mutex. because Rc objects just doesn't exposed out of Connection scope. so I am currently implementing future based neqo implementation(wrapping?) using async-std.

[iho]

so I am currently implementing future based neqo implementation(wrapping?) using async-std.

How it going? Do you need help? Can you share your work?

[ArtBlnd]

I am currently working neqo to support cross-compile. I have PoC but does not work well (it is for non-production at this time)

[xpepermint]

Any progress?

[ArtBlnd]

Sorry, I am about to use quinn so no progress :(

[larseggert]

The neqo demo client and server now use tokio, so this should be addressed.