Modify ↓
#120 closed task (fixed)Change the internals of YAM to use multithreading
Description
To move on, YAM requires to have internal multithreading (multiple Tasks/Processes). That means, the GUI operations have to be separated from the e.g. the TCP/IP transfer processing. Also, e.g. the background processing via the used timers can be put into an own process/Task. While we already have a preliminary "Threads" implementation, testing and more work have to go into it to make it more globally usable than it currently is. Attachments (0)Change History (10)comment:1 Changed 43 years ago by damato
comment:2 Changed 3 years ago by damato
comment:2 Changed 3 years ago by damato
comment:3 Changed 3 years ago by damato
comment:4 Changed 3 years ago by damato
comment:5 Changed 3 years ago by damato
(In #11) As we want to address that issue in 2.7 I am going to mark the milestone here and make it dependent on the multithreading information. comment:6 Changed 3 years ago by damato
(In #30) I'll flag that report for milestone 2.8 because we should have the multithreading functionality until then and can then rethink about how to improve the mail indexing. comment:7 Changed 3 years ago by damato
Since a few days we have a first working version of the multithreading functionality in the internals of YAM (see r4939). This flags a great milestone on the way to YAM 2.7+. The threading framework seems to work reliable so far thanks to lot of work from Thore. Therefore we can close this task and get the other tickets going which are blocked by this one. comment:8 Changed 3 years ago by damato
comment:9 Changed 17 months ago by damato
Note: See
TracTickets for help on using
tickets. | This list contains all users that will be notified about changes made to this ticket. These roles will be notified: Reporter, Owner, Subscriber
| ||||||||||||||||||||||||||||



(In #37) Since several years it has been one of the major goal to get IMAP4 support into YAM. However, as the protocol is quite complex and requires substantial changes to YAM this hasn't been achieved yet. However, by accepting this request it should be made clear that it is our goal to get that going.
Reference to the corresponding RFC: http://www.ietf.org/rfc/rfc2060.txt