Re: Connecting and account management

Philip Van Hoof wrote:

> The attached patch attacks a few of these problems already. It also
> deals with things that we'll need in future. For example letting the
> connection itself happen on the individual queues of each store account
> instance, in stead of in random threads.

That would be nice, because right now, if you have an account that
requires a lot of time to connect, the other accounts will be waiting
for a long time to connect despite having no problem.

> It also makes connecting happen reliably yet in parallel with other
> accounts. This improves the amount of time needed "to go online".
> This means that we can't detect when ALL accounts are connected. We can
> only detect when ONE account's connection state has changed.

Well this seems a MUA developer business, looks easy to manage at the
application side, and removes some annoying side effects, for example
the full reload of the folder store tree model when the connection
status of one account has changed.

> This is why there are significant adaptations to the folder store tree
> model too: the changes cope with connection state changes. The changes
> assume that if a store account goes online, it's possible that new
> folders will be available. Especially the first time the account is
> used, will this pull-in not yet seen folders.

Mmm, does this mean that the model will listen for changes in the
connection status of store accounts?

> This means that it's not needed to have a accounts-reloaded handler
> anymore. It is, however, now needed to add the created accounts manually
> to the TnyGtkFolderStoreTreeModel instance, as soon as you created it.

I don't really understand this. Currently he already have to do it. We
create the StoreTreeModel and then we call
tny_account_store_get_accounts passing the treemodel as second argument
to get the accounts from the store account.


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]