Discussion:
[castor-dev] GSOC =?GB2312?B?qEMgU2VsZi1JbnRyb2R1Y3Rpb24gYW5kIGFuIGluaXRpYWwg?= =?GB2312?B?cHJvcG9zYWwgZm9yICJSZWZhY3RvciBsb2NrIGVuZ2luZSI=?=
窦文生
2011-03-21 14:42:48 UTC
Permalink
Hi Ralf, and all

My name is Wensheng Dou, and I am a first-year Ph.D. student from
Institute of Software, Chinese Academy of Sciences in China. I am
interested in parallel and concurrent programming including programming
models, tool support, especially, refactoring for concurrency in Java.
And I want to get some practical experience about concurrency-aware
refactoring.

So I want to get involved in the GSoC2010 and contribute to open source
project, and I am interested in “Refactor lock engine” project. I think
this project could make me gain practical experience, and make Castor
more scalable, readable and maintainable, and gain good performance.

I have downloaded the Castor code (version 1.3.1, because the main
version does not work now, because of a maven build error), and I find
that Castor doesn’t use the java.util.concurrent library to improve the
performance (it uses some code from EDU.oswego.cs.dl.util.concurrent
library). The java.util.concurrent library provides flexible locking
constructs, more concurrent mechanism, and many lock-free and
thread-safe atomic data type. The java.util.concurrent library is very
useful to construct concurrent programs. I think Castor will benefit
from java.util.concurrent library.

I've read some documentations and some of the code of Castor and as per
my understanding, the outcomes of the project consists of the followings:

1. Remove the EDU.oswego.cs.dl.util.concurrent library, and use the
java.util.concurrent library to improve concurrency.
2. Find the shared data from the whole Castor project, and use atomic
data type or correct locks to protect them, and make the program
behavior-preserving, scalable.
3. Find the concurrency bugs in Castor JIRA, and repair these bugs.

After this project is done, Castor will use the java.util.concurrent
library to provide good performance, and I’ll gain more practice, which
will help me do my research.

I’ll investigate this project more deeply, and provide a more detailed
proposal for this project later.

Any comments and suggestions are welcome.
Thanks in advance for your feedback.


Best Regards,
Wensheng Dou


---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email
Ralf Joachim
2011-03-21 20:08:13 UTC
Permalink
Hi Wensheng Dou,

we appreciate your interest in this challenging project idea. The first
draft of your proposal looks quite promising. I'll contact you by
private mail within a few days to discuss your ideas.

Regards
Ralf
Post by 窦文生
Hi Ralf, and all
My name is Wensheng Dou, and I am a first-year Ph.D. student from
Institute of Software, Chinese Academy of Sciences in China. I am
interested in parallel and concurrent programming including programming
models, tool support, especially, refactoring for concurrency in Java.
And I want to get some practical experience about concurrency-aware
refactoring.
So I want to get involved in the GSoC2010 and contribute to open source
project, and I am interested in “Refactor lock engine” project. I think
this project could make me gain practical experience, and make Castor
more scalable, readable and maintainable, and gain good performance.
I have downloaded the Castor code (version 1.3.1, because the main
version does not work now, because of a maven build error), and I find
that Castor doesn’t use the java.util.concurrent library to improve the
performance (it uses some code from EDU.oswego.cs.dl.util.concurrent
library). The java.util.concurrent library provides flexible locking
constructs, more concurrent mechanism, and many lock-free and
thread-safe atomic data type. The java.util.concurrent library is very
useful to construct concurrent programs. I think Castor will benefit
from java.util.concurrent library.
I've read some documentations and some of the code of Castor and as per
1. Remove the EDU.oswego.cs.dl.util.concurrent library, and use the
java.util.concurrent library to improve concurrency.
2. Find the shared data from the whole Castor project, and use atomic
data type or correct locks to protect them, and make the program
behavior-preserving, scalable.
3. Find the concurrency bugs in Castor JIRA, and repair these bugs.
After this project is done, Castor will use the java.util.concurrent
library to provide good performance, and I’ll gain more practice, which
will help me do my research.
I’ll investigate this project more deeply, and provide a more detailed
proposal for this project later.
Any comments and suggestions are welcome.
Thanks in advance for your feedback.
Best Regards,
Wensheng Dou
---------------------------------------------------------------------
http://xircles.codehaus.org/manage_email
--
Syscon Ingenieurbüro für Meß- und Datentechnik GmbH
Ralf Joachim
Raiffeisenstraße 11
72127 Kusterdingen
Germany

Tel. +49 7071 3690 52
Mobil: +49 173 9630135
Fax +49 7071 3690 98

Internet: www.syscon.eu
E-Mail: ***@syscon.eu

Sitz der Gesellschaft: D-72127 Kusterdingen
Registereintrag: Amtsgericht Stuttgart, HRB 382295
Geschäftsleitung: Jens Joachim, Ralf Joachim


---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email
Loading...