johan...@sun.com wrote:
On Fri, Jun 26, 2009 at 12:07:13PM +0100, jmr wrote:
If api.info supported locking as does the rest of the API then the issue
we currently have with descriptions and licenses being fetched when a
user goes and does some other API action, would not arise. There might
be a slight delay in the progress starting but the GUI would still be
responsive. The API tasks are all being kicked off in background threads
and calling back to the GUI to update progress and so on.
I'm surprised you haven't filed a bug for this. I just filed:
9715 The info() operation should use the activity_lock
With regard to the CLI there should be no impact on acquiring the lock
as it is carrying out a single linear task and then exciting, unlike the
GUI which can be carrying out a number of tasks simultaneously and all
have to be managed, including keeping the GUI responsive and up to date.
Ok, but I don't think you answered my concern from the previous e-mail.
If the background thread is taking a long time to download manifests,
it's going to hold the activity lock and potentially starve out callers
who are trying to perform an install/update operation. How do you plan
to cope with this scenario?
Indeed, if info() holds an activity lock, then install and update
operations won't be able to start.
--
Shawn Walker
_______________________________________________
pkg-discuss mailing list
pkg-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
