nhyatt/putty-source
1
0
Fork 0
mirror of https://git.tartarus.org/simon/putty.git synced 2025-07-01 03:22:48 -05:00
Code Issues Projects Releases Wiki Activity

New Seat method, notify_remote_disconnect.

Browse Source 
This notifies the Seat that the entire backend session has finished
and closed its network connection - or rather, that it _might_ have
done, and that the frontend should check backend_connected() if it
wasn't planning to do so already.

The existing Seat implementations haven't needed this: the GUI ones
don't actually need to do anything specific when the network
connection goes away, and the CLI ones deal with it by being in charge
of their own event loop so that they can easily check
backend_connected() at every possible opportunity in any case. But I'm
about to introduce a new Seat implementation that does need to know
this, and doesn't have any other way to get notified of it.
This commit is contained in:
Simon Tatham
2021-05-22 12:47:51 +01:00
parent 62b694affc
commit 0553aec60a
15 changed files with 43 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

26
putty.h
View File

@ -924,6 +924,29 @@ struct SeatVtable {
*/
void (*notify_remote_exit)(Seat *seat);
/*
* Notify the seat that the whole connection has finished.
* (Distinct from notify_remote_exit, e.g. in the case where you
* have port forwardings still active when the main foreground
* session goes away: then you'd get notify_remote_exit when the
* foreground session dies, but notify_remote_disconnect when the
* last forwarding vanishes and the network connection actually
* closes.)
*
* This function might be called multiple times by accident; seats
* should be prepared to cope.
*
* More precisely: this function notifies the seat that
* backend_connected() might now return false where previously it
* returned true. (Note the 'might': an accidental duplicate call
* might happen when backend_connected() was already returning
* false. Or even, in weird situations, when it hadn't stopped
* returning true yet. The point is, when you get this
* notification, all it's really telling you is that it's worth
* _checking_ backend_connected, if you weren't already.)
*/
void (*notify_remote_disconnect)(Seat *seat);
/*
* Notify the seat that the connection has suffered a fatal error.
*/
@ -1095,6 +1118,8 @@ static inline int seat_get_userpass_input(
{ return seat->vt->get_userpass_input(seat, p, input); }
static inline void seat_notify_remote_exit(Seat *seat)
{ seat->vt->notify_remote_exit(seat); }
static inline void seat_notify_remote_disconnect(Seat *seat)
{ seat->vt->notify_remote_disconnect(seat); }
static inline void seat_update_specials_menu(Seat *seat)
{ seat->vt->update_specials_menu(seat); }
static inline char *seat_get_ttymode(Seat *seat, const char *mode)
@ -1163,6 +1188,7 @@ size_t nullseat_output(
bool nullseat_eof(Seat *seat);
int nullseat_get_userpass_input(Seat *seat, prompts_t *p, bufchain *input);
void nullseat_notify_remote_exit(Seat *seat);
void nullseat_notify_remote_disconnect(Seat *seat);
void nullseat_connection_fatal(Seat *seat, const char *message);
void nullseat_update_specials_menu(Seat *seat);
char *nullseat_get_ttymode(Seat *seat, const char *mode);