[
https://issues.apache.org/jira/browse/VCL-568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14235655#comment-14235655
]
ASF subversion and git services commented on VCL-568:
-----------------------------------------------------
Commit 1643337 from [~fapeeler] in branch 'vcl/trunk'
[ https://svn.apache.org/r1643337 ]
VCL-308, VCL-568
updated statements related to computerloadflow
As the loadstateid can change, need to insert based on name, not id's.
> refresh current reservations page 15 minutes after a reservation becomes
> available
> ----------------------------------------------------------------------------------
>
> Key: VCL-568
> URL: https://issues.apache.org/jira/browse/VCL-568
> Project: VCL
> Issue Type: Improvement
> Components: vcld (backend), web gui (frontend)
> Reporter: Josh Thompson
> Assignee: Josh Thompson
> Fix For: 2.4
>
>
> It would be useful to refresh the current reservations page shortly after a
> timeout could have occurred so that users will see if the reservation timed
> out.
> We'll key off events in computerloadlog.
> Two entries will be created in the variable table - acknowledgetimeout and
> connecttimeout that will have values that are the timeout period in seconds.
> One entry will be added to computerloadstate - connecttimeout.
> When vcld inserts the 'reserved' computerloadstate into computerloadlog, both
> vcld and the frontend will key off of that timestamp and
> variable.acknowledgetimeout to know when the reservation will timeout if the
> user does not click the Connect button.
> When the user clicks the Connect button, the frontend will insert an entry
> into computerloadlog for connecttimeout. Both vcld and the frontend will key
> off of that timestamp and variable.connecttimeout to know when the
> reservation will timeout if the user never connects.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
