[go: up one dir, main page]

Menu

#2 CHost::ReadFromString()

1.0
closed
None
2019-11-07
2019-11-07
No

please require 3rd column (~ tcp port) for UNIX sockets too
also please set CHost::m_Port from this field even for UNIX sockets (and even if it's zero)
this probably sounds weird, but some unix-socket =CHost=s are going to have TCP relays wrapping them, and I want to be able to grab the port-number of the TCP relay from the "status" request responses (assuming it was stored correctly in the *.cfg file). This is especially important for the transition period between TCP- and UNIX-sockets.
I know I wrote "port field is not needed", but I probably should have said "port field should be ignored" (I believe my examples all included a 3rd field with a "dummy placeholder" string "-")
this should actually make the code a bit less complicated, and makes parsing *.cfg files with external scripts (which I need to do fairly often) much easier!

Discussion

  • Alexey Sokirko

    Alexey Sokirko - 2019-11-07
    • assigned_to: Bryan Jurish
     
  • Alexey Sokirko

    Alexey Sokirko - 2019-11-07
    • status: open --> closed
     

Log in to post a comment.