users dropped with no feedback

[Mark Ramm]

Neither the server nor the client users are given any feedback when a connection is dropped. The only way to tell that you aren't on gobby session anymore is to notice that someone else's gobby edit is not showing up on your screen.

[Philipp Kern (pkern)]

This is the behaviour of TCP. When the protocol layers notices that the corresponding host is down, it will terminate the connection on the server side and the others will notice. There is currently no possibility to check an open connection, but perhaps we'll include keep-alives in 0.4.0.

[Mark Ramm (mark-ramm)]

> Comment:
> This is the behaviour of TCP. When the protocol layers notices that the
> corresponding host is down, it will terminate the connection on the
> server side and the others will notice. There is currently no
> possibility to check an open connection, but perhaps we'll include keep-
> alives in 0.4.0.

I understand, but keep-alives, heartbeats, or something ought to be
used to provide a user with feedback that his work is no-longer being
shared. Especially since there's no way to rejoin the connection
without losing that work.

--Mark

[Philipp Kern (pkern)]

There is since 0.3.0: Users could serialise their sessions into files and restore them by hosting a new session.

[Philipp Kern (pkern)]

But not if they are just clients... This has to be fixed, and it will be, as soon as a solution is found.

[Philipp Kern (pkern)]

A ticket about this issue has been filed in upstream's bugtracker.

[armin (armin-gobby-bugs)]

Wouldn't it better to implement this right away in net6? The only problem would be that net6 would have to add a timer to send requests periodically and close the connection after some time without reply. Could be a requirement for the selector.

[obby (obby-gobby-bugs)]

(In [852]) /gobby: changeset Added timeout capability to GSelector, enable keepalives [fixes #131]
Original author: Armin Burgmeier <[e-mail]>
Date: 2006-03-27 15:29:43

[Philipp Kern (pkern)]

Fixed upstream

[Philipp Kern (pkern)]

No, the fix is not yet "released", just committed upstream. Sorry. Resetting back to "In Progress".

[Rocco Stanzione (trappist)]

The appropriate status for this is "fix committed" - or was, back in March. The fixed version is in Edgy - does the problem exist in Dapper?

[William Grant (wgrant)]

Fixed in Edgy.

[launchpad (launchpad-gobby-bugs)]

Updating Launchpad bug reference