> I would rather just see you get it working good enough that
> you feel good about getting rid of the old code. I would
> think that the saving of the cache would still be something
> we need/want.
> > So far everything seem to work fine, but I'd rather test it for few
> > more
> > so I'm not going to post any broken code ...
> > If everything will work as I expect, I believe that the both
> > correctness
> > performance of the synchronization stuff will be improved
> noticably ...
> It all sounds good. I do not mind helping you test if you
> want to send it to me.
Here it is.
I've tested it and was so far pretty happy with it.
Just 2 minor things:
- when there is an incoming change in some dir, and you do an update in
syncView on that incoming file,
the Project remains to stay in the syncView. However when you do an update
on the dir or the project itself,
It disappears as expected. It's minor, I'll look at it later.
- second, during development I had problems with deadlock on synchronized
methods. I've rewritten the code,
and it seems to work fine since then.
Just in case eclipse freezes, it theory might be caused by the
flushPendingCache stuff (but I think it should not anymore).
Could you please test it too ?
Received on Thu Jul 7 22:31:19 2005