Document LazyConfigAcceptor

Open
  • Is something wrong?
#8 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
Half a day
Newbie friendliness
45/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Tech stack
rust
Domain
documentation

Research direction

Start with the linked docs.rs page for LazyConfigAcceptor and compare it with the TlsAcceptor documentation. Update the project documentation to explain what LazyConfigAcceptor does and when it is more appropriate than TlsAcceptor directly; done means both the behavior and choice are clear to readers.

Written by the indexing model from the issue text.

Description

Hi! What does LazyConfigAcceptor do? When would it be more appropriate to use LazyConfigAcceptor instead of using TlsAcceptor directly?

Dominant language
Rust
Stars
22
Forks
9
Avg merge
5d 4h
Merged PRs (30d)
3

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from rustls/futures-rustls

All issues in rustls/futures-rustls

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.