Enhancement: Option to insert delay between each byte send
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 57
- Forks
- 36
- PR merge metrics
- No merged PRs in 30d
Description
For legacy telnet servers such as rmenu (FreeDOS), client data is often lost when sent too quickly. This happens even though the connection is TCP. So, it would be nice if net-telnet offered a configuration option for the client object, to wait that many seconds between each byte sent to the telnet server. This significantly improves data integrity.
For example, telnet clients running commands on FreeDOS servers, should wait about 1-2 seconds between each (hot)key press. What do you think, could net-telnet get this kind of configuration parameter?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the net-telnet client path that sends data to the server and review how client configuration is represented. Define how a per-byte delay should behave, including the seconds-based value described for legacy FreeDOS telnet servers, then verify that transmitted command input is spaced accordingly without changing the default behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100