Re: threads in jCVS (was: jCVS version using Swing UI available)

[time@ice.com]

> > If you intend to continue to hack on jCVS, we should talk
> > so that we can coordinate our activities. I am in the process
> > of making the CVS repository for jCVS publicly available.
> 
> There are a lot of things I want to hack on currently :)
> One thing in particular, making jCVS use multiple threads (or at
> least one for the network and one for the display) is on my mind.
> But since you're working on a new major release, perhaps you have
> done that already?

I have done some work, yes. The current strategy is to separate the
ui from the communications so that the screen will update and the
user can "cancel" a command.

The current design, therefore, gives a thread to every CVSClient for
every open project window. This allows you to do a checkout in one
project while committing another.

This raises lots of issues with coordinating the Entries files and
their access, but this is already an (unaddressed I'm afraid) issue,
since a user can open multiple projects any one of which can be a
subtree of another project. So far, no reports of problems (as he
knocks on simulated wood :). It also involves placing the ui in a
"state" where commands are not processed except "cancel".

What are your thoughts?

Also, I am going to start cc-ing this thread to the jcvs development
mailing list, if you do not mind. I like to archive these important
discussions.

tim.
Tim Endres, ICE Engineering, Inc.
   mailto: time@ice.com    http://www.ice.com
   "Usenet - A slow moving self parody." -- Peter Honeyman