[Feature Request]: Show status info on Exchange position and Exchange user info

[pedjas]

Contact Details

No response

Tell us your idea.

When I click on Exchange position and Exchange user info in application and monitor traffic on other node and I see packets properly sent.

But, in application itself there are no visual clues. It is like nothing happened.

It would be good to have popup like with Traceroute to show what is sent, and if sending info went through.

Relevant log output

Code of Conduct

• I agree to follow this project's Code of Conduct

[DaneEvans]

#2740 Adresses this for metadata.

I'm still not convinced by this at all.

2s transmission time,
2 ( 7 hops x 2 + retries (0..2) ) + network congestion etc.
= 28-32 + congestion S delays

Unless we don't block UI, and interrupt when the packet is recieved, adding these will make for an awful UX

[prokrypt]

Idea: in the node details page, have the Exchange position/userinfo and Request Metadata buttons do a short timeout (like on the Traceroutes button) to indicate a successful activation and to prevent accidental double-taps. For the regular pop-up menu there is no need for indication as the menu disappears when an action is selected.

[pedjas]

#2740 Adresses this for metadata.

I'm still not convinced by this at all.

2s transmission time, 2 ( 7 hops x 2 + retries (0..2) ) + network congestion etc. = 28-32 + congestion S delays

Unless we don't block UI, and interrupt when the packet is recieved, adding these will make for an awful UX

I am not sure to understand. I am not proposing additional traffic, just visual clue that process is executed.

[jamesarich]

#2740 Adresses this for metadata.
I'm still not convinced by this at all.
2s transmission time, 2 ( 7 hops x 2 + retries (0..2) ) + network congestion etc. = 28-32 + congestion S delays
Unless we don't block UI, and interrupt when the packet is recieved, adding these will make for an awful UX

I am not sure to understand. I am not proposing additional traffic, just visual clue that process is executed.

Without the actual firmware support, we would be blocking ui falsely for an arbitrary timeout for no real purpose - the packet is sent, if you get a response - the ui updates (access to remote admin). if you don't it doesn't. This isn't a hard concept.

[pedjas]

I am 40 years in software development (mainly doing UI) and this is the first time I hear about concept that when user clicks a button to initiate something to happen, it is wrong that he gets visual confirmation that operation is actually executed.

[DaneEvans]

Really? So interrupts, multiple threads? none of that rings a bell?
Have you tried traceroute on a long (2+ hop ) route?

The realities of a slow network make it a poor idea to block UI waiting for return packets.
Putting a cooldown on the button, that we could do. But waiting for a response is going to be like working on a 9k dialup connection.

[pedjas]

Maybe we are talking about different things? My point is when I click button I have no feedback that anything happens. I end up pressing button few times thinking I did not click it.

[pedjas]

With 2.7.2 version of app this is resolved in a manner, as now connection icon flashes when something happens with connection like sending and receiving data. So now there is visual clue that something is going on.