2026/09/01

From WoozleCodes
Jump to navigation Jump to search
Tuesday, September 1, 2026 (#244)
Monday Tuesday Wednesday

References

Main Work

Currently doing a careful re-think of how Ferreteria connection-sessions are structured.

Despite the table currently claiming that the Starter does proc_open() and proc_close(), it is actually the Session doing that. I'm thinking this is part of the problem I'm currently dealing with.

What if we have (as originally laid out on 2026/08/31):

  • create connection object
  • open the connection
  • for each command over the same connection:
    • open a stream to receive responses
    • send the command
    • read the responses
    • [send additional requests]
    • [receive additional responses]
    • close the stream
  • close the connection

Current table (to be modified):

Details: API Proc SSH2
Model Action Starter Session Starter Session
Open Session->Connectify() NO OP create Session object ssh2_connect()
Run Session->StartProcess() proc_open() send to stdin forward to Session object ssh2_exec()
recv Session->OExecLecture stdout
send Session->OExecRespond stdin
Shut Session->ActualShut() proc_close() zap Session object ssh2_​disconnect()