peer info in user interface #32

New Issue

zooko · 2007-05-04T05:22:57Z

zooko commented

2007-05-04 05:22:57 +00:00

It would be cool if peer info such as IP address, how long I've been connected to them, or any other such information that is available could be displayed in the UI.

zooko added the

code

minor

enhancement

labels 2007-05-04 05:22:57 +00:00

zooko self-assigned this 2007-05-04 05:22:57 +00:00

warner commented

2007-05-08 02:27:45 +00:00

It would be nice if the list-of-all-peers that you see on the web frontend could include two timestamps: one indicating how long that peer has been attached, and a second that indicates how long it has been since we've heard from that peer. The former should be recorded in and obtained from the IntroducerClient class. The latter should be extracted from Foolscap-0.1.3's dataLastReceivedAt attribute (but foolscap should provide a clean accessor for it).

The central introducer node should have a small web ui where it can display the same information. The foolscap-vs-NAT issues that ought to be addressed by the keepalives introduced in foolscap-0.1.3 would be easier to examine and verify if we had such timestamps visible.

It would be nice if the list-of-all-peers that you see on the web frontend could include two timestamps: one indicating how long that peer has been attached, and a second that indicates how long it has been since we've heard from that peer. The former should be recorded in and obtained from the [IntroducerClient](wiki/IntroducerClient) class. The latter should be extracted from Foolscap-0.1.3's dataLastReceivedAt attribute (but foolscap should provide a clean accessor for it). The central introducer node should have a small web ui where it can display the same information. The foolscap-vs-NAT issues that ought to be addressed by the keepalives introduced in foolscap-0.1.3 would be easier to examine and verify if we had such timestamps visible.

zooko was unassigned by warner

2007-05-08 02:27:45 +00:00

warner self-assigned this 2007-05-08 02:27:45 +00:00

zooko commented

2007-07-01 03:26:41 +00:00

I was just showing Sam Stoller how Tahoe works, and I uploaded a file, and there was only one node on the network (my node, on my local demo network), so I wasn't actually achieving any "backup" functionality, but the user interface made it appear as though I was.

So if the information about which peers it is uploading to (successfully) should be displayed as part of the upload UI.

I was just showing Sam Stoller how Tahoe works, and I uploaded a file, and there was only one node on the network (my node, on my local demo network), so I wasn't actually achieving any "backup" functionality, but the user interface made it appear as though I was. So if the information about which peers it is uploading to (successfully) should be displayed as part of the upload UI.

warner commented

2007-07-25 03:35:55 +00:00

I've created #92 to cover that second goal: after upload, display which peers were used and how many shares went to whom.

I'll leave this one (#32) for enhancing the welcome.xhtml page to show per-peer information like how long you've been connected to them, a name they might publish ("Bob's Laptop"), maybe stuff about what kind of reliability your node assigns to them.

Of course, this information could also be shown on the #92 post-POST page, for the peers that were used, but #32 is for the data shown that's completely outside the scope of an upload operation.

I've created #92 to cover that second goal: after upload, display which peers were used and how many shares went to whom. I'll leave this one (#32) for enhancing the welcome.xhtml page to show per-peer information like how long you've been connected to them, a name they might publish ("Bob's Laptop"), maybe stuff about what kind of reliability your node assigns to them. Of course, this information could also be shown on the #92 post-POST page, for the peers that were used, but #32 is for the data shown that's completely outside the scope of an upload operation.

warner added the

0.4.0

label 2007-07-25 03:35:55 +00:00

warner commented

2007-08-09 20:14:29 +00:00

#96 is related: there are many use cases where you really don't want to upload anything to yourself, and in these there should be a switch to turn such uploads off before they happen, rather than simply informing you about it after the fact.

warner added

code-frontend-web

and removed

code

labels 2007-08-14 18:55:59 +00:00

zooko commented

2007-09-25 04:26:30 +00:00

I think of this as part of the "introduction/resource management/friendnet/deletion/etc." task. Assigning to Milestone 0.7.0.

zooko added

0.6.0

and removed

0.4.0

labels 2007-09-25 04:26:30 +00:00

zooko added this to the 0.7.0 milestone 2007-09-25 04:26:30 +00:00

zooko commented

2007-11-01 18:15:07 +00:00

We're focussing on an imminent v0.7.0 (see the roadmap) which hopefully has [#197 #197 -- Small Distributed Mutable Files] and also a fix for [#199 #199 -- bad SHA-256]. So I'm bumping less urgent tickets to v0.7.1.

We're focussing on an imminent v0.7.0 (see [the roadmap](http://allmydata.org/trac/tahoe/roadmap)) which hopefully has [#197 #197 -- Small Distributed Mutable Files] and also a fix for [#199 #199 -- bad SHA-256]. So I'm bumping less urgent tickets to v0.7.1.

zooko added

0.6.1

and removed

0.6.0

labels 2007-11-01 18:15:07 +00:00

zooko commented

2007-11-13 18:27:13 +00:00

We need to choose a manageable subset of desired improvements for [ http://allmydata.org/trac/tahoe/milestone/0.7.1 v0.7.1], scheduled for two week hence, so I'm bumping this one into v0.7.2, scheduled for mid-December.

We need to choose a manageable subset of desired improvements for [ <http://allmydata.org/trac/tahoe/milestone/0.7.1> v0.7.1], scheduled for two week hence, so I'm bumping this one into [v0.7.2](http://allmydata.org/trac/tahoe/milestone/0.7.2), scheduled for mid-December.

zooko added

0.7.0

and removed

0.6.1

labels 2007-11-13 18:27:13 +00:00

zooko added this to the undecided milestone 2008-01-23 04:19:15 +00:00

zooko commented

2008-01-26 00:27:01 +00:00

Merging in #286 -- "display IP address of peers in Welcome page, other info like nickname too?"

warner commented

2008-02-13 01:42:18 +00:00

The welcome page now displays nodeid, nickname, and connection time. It
doesn't yet ask foolscap for the last-heard-from time. I'm creating a new
(minor) ticket for that one: #311.

Upload results are listed in a separate ticket (#92) and are half-implemented
now, so I'm closing this one out.

The welcome page now displays nodeid, nickname, and connection time. It doesn't yet ask foolscap for the last-heard-from time. I'm creating a new (minor) ticket for that one: #311. Upload results are listed in a separate ticket (#92) and are half-implemented now, so I'm closing this one out.

warner added the

fixed

label 2008-02-13 01:42:18 +00:00

warner closed this issue

2008-02-13 01:42:18 +00:00

Sign in to join this conversation.