<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
I might be wrong, but:<br>
<br>
"At the moment, we don't have a way to control this queue, when it's
necessary, the frontend try to do it. The problem is when the user
wants to trigger more then one task, then he can't make a logout in
the system because he will lose this queue."<br>
<br>
Is the task bind to the user session in a way that if I fire up a
task from<br>
the UI and logout the task is gone?<br>
<br>
<div class="moz-cite-prefix">On 07/11/2016 04:11 PM, Peter Pennings
wrote:<br>
</div>
<blockquote
cite="mid:CAA81Kx_j0dW7f1DhYyNLQASpKK96nfuUVT3k-zhqpJcMDXHT5A@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>Hey guys,</div>
<div><br>
</div>
We want to suggest here a new discussion which can maybe turn
into a new feature to improve the system.
<div><br>
</div>
<div>During the development of some activities involving
assincronous tasks, we were thinking about a new way to manage
a tasks queue and a new way to get informed about the tasks in
the system.</div>
<div><br>
</div>
<div>We divided the idea into two parts:<br>
</div>
<div><br>
</div>
<div><b>1-)</b> First of all, an idea to the backend take care
of a tasks queue, allowing the user to trigger tasks as many
as he wants. Any request involving an async task triggered by
the user, will be pushed into a queue in the back-end. There
will be a consumer of this queue, getting the first task to
process, and the others will be set with a "Waiting" status.
This "consumer" will manage the queue of tasks. One idea to
implement this is using the "Publish Subscribe" Desing
Pattern. Another idea is to keep the task with a "Waiting"
status in the database, and the consumer consumes from this
database instead of a queue (updating the status and message
of the task). </div>
<div>At the moment, we don't have a way to control this queue,
when it's necessary, the frontend try to do it. The problem is
when the user wants to trigger more then one task, then he
can't make a logout in the system because he will lose this
queue.</div>
<div><br>
</div>
<div><b>2-)</b> Develop a new tab in Wok to show the tasks in
the system. We can show the tasks for each plugin separeted.
For example: if the user has kimchi, ginger and gingerbase
installed, this tab will contain three sections, each one with
a table of tasks containg the id, status (running, waiting,
failure, etc), message and target uri of each task. We can
develop a filter for this tables too, allowing the user to
search the tasks respecting some filters.</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div>The main idea with this suggestion, is a way to display
what is happening in the system with the async tasks and allow
the user to make more then one async request without waiting
for the last getting finished.</div>
<div><br>
</div>
<div>All of this is just a suggestion, we are open to any doubts
or to discuss and improve this idea. Feel free to any
suggestions or criticizes. :)</div>
<div><br>
</div>
<div>Thank you.</div>
<div><br>
</div>
<div>Peter Pennings</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Kimchi-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Kimchi-devel@ovirt.org">Kimchi-devel@ovirt.org</a>
<a class="moz-txt-link-freetext" href="http://lists.ovirt.org/mailman/listinfo/kimchi-devel">http://lists.ovirt.org/mailman/listinfo/kimchi-devel</a>
</pre>
</blockquote>
<br>
</body>
</html>