Skip to content

bshow next transaction time when sending message - #127

Open
duy wants to merge 1 commit into
agl:masterfrom
duy:nexttransactiontime
Open

bshow next transaction time when sending message#127
duy wants to merge 1 commit into
agl:masterfrom
duy:nexttransactiontime

Conversation

@duy

@duy duy commented Sep 26, 2014

Copy link
Copy Markdown
Contributor
  • add nextTransactionTime variable to the client to store the next transaction absolute time
  • show when next transaction will happen in the "Created new outbox..." message
  • remove second decimals from "Next network transaction..." log message

 * add nextTransactionTime variable to the client to store the next transaction absolute time
 * show when next transaction will happen in the "Created new outbox..." message
 * remove second decimals from "Next network transaction..." log message
@burdges

burdges commented Nov 28, 2014

Copy link
Copy Markdown
Contributor

I suspect this patch does not provide the information intended :

Pond's next transaction might not send the message you've just "sent" either because you've multiple messages in the queue already or (I think) even because your next transaction is a fetch not a send.

In principle, you could reasonably display this time if (a) no messages are currently in the queue and (b) the next transaction would be a send. If (a) fails, maybe you'd want to say how many messages are ahead of it in the queue. If only (b) fails, then maybe you'd want to say "approximately" nextTransactionTime + 5min.

I donno if @agl had other concerns with this patch besides those.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants