On 06/26/09 15:55, Shawn Walker wrote:
On Jun 26, 2009, at 6:07 AM, 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.
It seems reasonable to have api.info() do locking since it supports
queries of multiple packages at a time.
However, what happens to the GUI threads that sit there waiting for an
api call that may not return for 15-20 minutes while the
install/update is going?
The user cannot interact with the GUI while install/update is working so
if this happens the user will not notice.
Padraig
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
