View Issue Details

IDProjectCategoryView StatusLast Update
0000789LDMudNetworkingpublic2022-10-06 18:09
Reporter_xtian_ Assigned ToGnomi  
PrioritynormalSeverityfeatureReproducibilityN/A
Status closedResolutionunable to reproduce 
Summary0000789: change driver-handling to linemode (without sending telnet negs)
DescriptionI am looking for a way to change the driver-handling from linemode/charmode without sending telnet-negs to the client. My solution is as of now:

  input_to("nofun_telnet",
           INPUT_APPEND|
           INPUT_NO_TELNET);
  remove_input_to( this_object() );

But, unfortunately, player input may still end-up in the nofun_telnet()-function sometimes (ie there is a concurrency issue).

So, another way to notify the driver that I am expecting linemode now would be nice. If you see a better way to achieve this with the means already built-in, that would also be appreciated.

Background: After I have identified Win-Telnet (this is done with charmode input_tos without telnet negs), I want to switch back the driver to linemode without using telnet negs. The idea is to NOT send telnet negs to win-telnet, ever.

I do all telnet neg handling in the mudlib.
Tagsdiscussion
External Data (URL)

Activities

zesstra

2011-10-31 12:55

administrator   ~0002072

I thought the driver automatically switches back into linemode once the input_to with charmode finished? At least the manpage reads like that. Is that wrong?

_xtian_

2011-10-31 19:34

reporter   ~0002073

Yes, but the question is in what mode the driver is on a virgin connection.
Note that there have been no prior telnet negotiations at this point.

Gnomi

2021-04-18 18:36

manager   ~0002628

I'm not sure what we are talking about.
1. The driver's handling of incoming data: Processing that as a line or character and forward it to the corresponding actions or input_tos.
2. Sending the telnet negotiations out that are needed for pending input_tos/actions
3. Calling the H_NOECHO hook with different flags

What would you like to have changed?

Gnomi

2022-10-06 18:09

manager   ~0002687

Closing this, as we don't understand what needs to be fixed.
Please reopen this issue with further information if you feel this issue still persists.

Issue History

Date Modified Username Field Change
2011-10-27 09:21 _xtian_ New Issue
2011-10-31 12:55 zesstra Note Added: 0002072
2011-10-31 19:34 _xtian_ Note Added: 0002073
2021-04-16 18:12 zesstra Tag Attached: discussion
2021-04-18 18:36 Gnomi Status new => feedback
2021-04-18 18:36 Gnomi Note Added: 0002628
2022-10-06 18:09 Gnomi Assigned To => Gnomi
2022-10-06 18:09 Gnomi Status feedback => closed
2022-10-06 18:09 Gnomi Resolution open => unable to reproduce
2022-10-06 18:09 Gnomi Note Added: 0002687