[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
|
[mylar-dev] I/O cancellation handling
|
- From: "Willian Mitsuda" <wmitsuda@xxxxxxxxx>
- Date: Tue, 16 Jan 2007 14:21:19 -0200
- Delivered-to: mylar-dev@eclipse.org
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=JGJQkaQ8tE0zbw3NhVg5d9g0wlI6x55dHNFEhcd50jR6DHQz7xThCRT5XDiz35BuSnQj32ecnaBvd9fPEerafMjbf00CCCk5gS9mDiPMr0GpZ1e2N3VJlogQ2c3ODiYiA5cjdwnUa8QEZBY1xtkzXRc91yAqncgm2A3uSFGa6B0=
Hi,
I saw that there are some bugs opened regarding handling of repository
communication cancellation, and this was discussed on last meeting
(http://wiki.eclipse.org/index.php/Mylar_Meetings#Tuesday.2C_Januray_9.2C_10-11am_PT).
I just saw Michael Valenta's post about communication error handling:
http://eclipselowdown.blogspot.com/2007/01/responsive-remote-connections.html
and I think perhaps some concepts could be useful.
For instance, I'm handling bug#162608,
(https://bugs.eclipse.org/bugs/show_bug.cgi?id=162608) and depending
on what I get as soon as I resubmit the patch (perhaps next week),
I'll keep you posted.
There are some bugs/plans to unify error/operation handling, and
having something unified to handle progress/cancellation can be useful
too.