add "last-heard-from" timestamp to welcome page #311

Closed
opened 2008-02-13 01:41:58 +00:00 by warner · 5 comments

The welcome page currently lists all storage servers that we're connected to. It should ask Foolscap for the last-heard-from timestamp (which should be less than 10 minutes for real connections, since the keepalives insure that we'll get some amount of traffic at least that frequently) and display it in the same table.

This requires support from Foolscap, probably in the form of rref.getLastHeardFromTime() or something.

The welcome page currently lists all storage servers that we're connected to. It should ask Foolscap for the last-heard-from timestamp (which should be less than 10 minutes for real connections, since the keepalives insure that we'll get some amount of traffic at least that frequently) and display it in the same table. This requires support from Foolscap, probably in the form of `rref.getLastHeardFromTime()` or something.
warner added the
code-network
minor
enhancement
0.7.0
labels 2008-02-13 01:41:58 +00:00
warner added this to the eventually milestone 2008-02-13 01:41:58 +00:00
warner self-assigned this 2008-02-13 01:41:58 +00:00

If you like this ticket you might also like #816 (Add ping-all-servers button to welcome page).

If you like this ticket you might also like #816 (Add ping-all-servers button to welcome page).

I opened foolscap #169 to request this feature.

I opened [foolscap #169](http://foolscap.lothar.com/trac/ticket/169) to request this feature.
Author

foolscap#169 is fixed as of version 0.6.1

The new method name is rref.getDataLastReceivedAt()

[foolscap#169](http://foolscap.lothar.com/trac/ticket/169) is fixed as of version 0.6.1 The new method name is `rref.getDataLastReceivedAt()`
davidsarah commented 2011-12-29 02:47:06 +00:00
Owner

Note that we depend on foolscap >= 0.6.1, so we can use this feature now without raising the dependency.

Note that we depend on foolscap >= 0.6.1, so we can use this feature now without raising the dependency.
tahoe-lafs modified the milestone from eventually to 1.10.0 2011-12-29 02:47:06 +00:00
daira commented 2013-05-19 13:42:36 +00:00
Owner

Merging this into #1973.

Merging this into #1973.
tahoe-lafs added the
duplicate
label 2013-05-19 13:42:36 +00:00
daira closed this issue 2013-05-19 13:42:36 +00:00
Sign in to join this conversation.
No Milestone
No Assignees
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Reference: tahoe-lafs/trac-2024-07-25#311
No description provided.