Good idea!  I made the following changes to the web code:

- if you click "show name" in the task list, tasks are sorted
  by name instead of ID

- you can search for tasks by name.

This is deployed on SETI@home and SETI@home beta.

-- David

On 08-Sep-2013 1:22 PM, Richard Haselgrove wrote:
This looks very useful, both for application developers/testers, and when
helping volunteers diagnose faults via a project message board.

But either process is slowed down and made harder by a missing link in the 
chain.

The local client knows a task only by its name, as in the list below.
The project website default display (except at Einstein) displays Task IDs for
results - and always displays tasks in order of ID #, even when displaying 
names.

It would be most helpful to be able to associate names and Task IDs - either by
passing the Task ID # to the client in the <result> block when allocating the
task, or by adding a task name search facility to the task listing pages on
project websites.

    
--------------------------------------------------------------------------------
    *From:* David Anderson <[email protected]>
    *To:* BOINC Developers Mailing List <[email protected]>
    *Sent:* Sunday, 8 September 2013, 20:54
    *Subject:* [boinc_dev] new GUI RPC for getting completed /reported tasks

    Fred (developer of BoincTasks) pointed out that it's hard for GUIs
    to learn the outcome of completed tasks,
    since the interval from when the task completes to when it's reported
    can be just a few seconds,
    and after this the client forgets about the task.

    To address this problem, I did the following:

    - the client keeps an in-memory list of tasks that have been reported
       in the last hour.
       For each tasks it stores
       - the project URL
       - the result name
       - the app name
       - the final elapsed time
       - the exit status
       - the time when the task completed
       - the time when the task was reported

    - There's a new GUI RPC, get_old_tasks(), which fetches this list.

    This feature will be in the next client release.

    -- David
    _______________________________________________
    boinc_dev mailing list
    [email protected] <mailto:[email protected]>
    http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
    To unsubscribe, visit the above URL and
    (near bottom of page) enter your email address.


_______________________________________________
boinc_dev mailing list
[email protected]
http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.

Reply via email to