66 |
Past: |
Past: |
67 |
============= |
============= |
68 |
|
|
69 |
|
2003-07-14 - 2003-07-15 |
70 |
|
- start looking for merge/versioning stuff |
71 |
|
- few refs to .bib file |
72 |
|
- de-centralized RCSs: |
73 |
|
- DARCS (http://www.abridgegame.org/darcs/) |
74 |
|
- arch (http://arch.fifthvision.net/bin/view) |
75 |
|
- arx (http://arch.fifthvision.net/bin/view) |
76 |
|
- monotone (http://www.venge.net/monotone/) |
77 |
|
- codeville (http://bitconjurer.org/codeville/) |
78 |
|
- study the star topology merge problem |
79 |
|
- at the center is a "central branch" |
80 |
|
- additionally, there are a number of branches which |
81 |
|
form a "star" around the "central branch" |
82 |
|
- study multi-branch merging |
83 |
|
- merging various branches whilen each of the |
84 |
|
branches have previously merged with |
85 |
|
some of the others |
86 |
|
- study the theory behind DARCS |
87 |
|
- DARCS and arch seem most promising w.r.t. advanced merging/versioning |
88 |
|
techiques, OTOH monotone uses SHA-1 IDs for different versions |
89 |
|
of a file (and as we know, Storm uses SHA-1 for creating IDs) |
90 |
|
- arch/DARCS resemble BitKeeper |
91 |
|
|
92 |
|
2003-07-09 - 2003-07-11 |
93 |
|
- look more carefully SEDA/Sandstorm threading model |
94 |
|
- YES, we can use Sandstorm's threads concurrently |
95 |
|
with native (Java) threads (as long as we give |
96 |
|
sleep/yield threads occasionally)! |
97 |
|
- YES, we are able to use Tapestry with Storm/Fenfire! |
98 |
|
- finish the PEG from this part, i.e., wait for Tuomas' |
99 |
|
comments |
100 |
|
|
101 |
|
|
102 |
2003-07-03 - 2003-07-8 |
2003-07-03 - 2003-07-8 |
103 |
- a PEG about using Tapestry with Storm |
- a PEG about using Tapestry with Storm |
104 |
- Intro to Tapestry/SEDA/Tapestry API |
- Intro to Tapestry/SEDA/Tapestry API |