Re: [orion-dev] progress service - meeting mintes

[Szymon Brandys <Szymon.Brandys@xxxxxxxxxx>]

I would use the word "operation".
I think this is what we use in Eclipse Desktop in Progress View.
--
Szymon



From:      
 Susan Franklin McCourt
<susan_franklin@xxxxxxxxxx>
To:      
 Orion developer discussions
<orion-dev@xxxxxxxxxxx>
Date:      
 2011-12-05 20:56
Subject:    
   Re: [orion-dev]
progress service - meeting mintes
Sent by:    
   orion-dev-bounces@xxxxxxxxxxx

---

I was talking to Szymon a little bit after the call, and
a terminology problem became apparent.
We often use the word "task" at a high level to talk about what
a user is doing (resource + task = page, etc.)
When I spoke of a topic system for user tasks, I was referring to the high
level user task. This is a concept we can use for contextual page links,
etc. It's not really talking about "programmatic tasks" though
we spoke of using this topic system when registering programmatic tasks,
as a way of deciding whether I should show details about this programmatic
task to a user on a particular page.

So we need separate terms for "the programmatic task" on which
we are having progress, status, etc....and the "user task" that
a particular page is trying to offer a user.
Maybe separate nouns?

susan

Malgorzata
Tomczyk ---12/05/2011 10:57:39 AM---- We could call it "status service"
rather than a "progress service" because we don't necessary need

From: Malgorzata Tomczyk <Malgorzata.Janczarska@xxxxxxxxxx>
To: Orion developer discussions <orion-dev@xxxxxxxxxxx>
Date: 12/05/2011 10:57 AM
Subject: [orion-dev] progress service - meeting mintes
Sent by: orion-dev-bounces@xxxxxxxxxxx

---

- We could call it "status service" rather than a "progress
service"
because we don't necessary need progress information, but status: running,
finished
- There are two kind of tasks
- "global tasks" - tasks that need to finish, they may be interesting
for pages other than page that started them: git clone, compile etc
- "page tasks" - tasks that are interested only for the page
that
started them: listing files, git log etc
- All asynchronous operations could be considered as "page tasks",
we could
use dojo.Deferred to track them
- Client should decide in the scope of the operation (global task or page
task)
- What about tasks that says "runnig" for 10 days? Should we
have a timeout
after which we say we don't track the task any more, because it probably
hanged and we don't care for it any more?
- We could provide a cancellation or "cancellation with forget"
- meaning
we don't want to here about this task any more
- Should we get rid of old tasks after some time?
- We could create a "topic system" for tasks. Each task would
have a list
of topics than it refers to. Pages could register for topics and display
progress of the topics they are interested in. They could also react for
completion of some of those tasks.
- Progress service should report errors of tasks

plans:
M1: all calls to progress service should be moved to plugin:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=365644
M1: a global list that gathers tasks from the servers
https://bugs.eclipse.org/bugs/show_bug.cgi?id=364987

Future (M2?)
List of tasks stored on the client site (local storage). This tasks list
could be listened by client pages to get updates for tasks they started
and
tasks from topics they are interested in.

Tasks API (server):
https://bugs.eclipse.org/bugs/show_bug.cgi?id=364830

Malgorzata (Gosia) Janczarska
Software Developer
IBM SWG Lab. Cracow. Poland

IBM Polska Sp. z o.o. oddział w Krakowie
ul. Armii Krajowej 18,
30-150 Kraków

NIP: 526-030-07-24
Sąd Rejonowy dla m.st. Warszawy, XII Wydział Gospodarczy KRS
KRS 0000012941, Kapitał Zakładowy: 33.000.000 PLN

_______________________________________________
orion-dev mailing list
orion-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/orion-dev

_______________________________________________
orion-dev mailing list
orion-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/orion-dev