Hey,
> but there is another issue regarding Windows yet, I
> also have not set the mutexes in the compiler parts
> to avoid windows filelocking if more than one user
> hits the server.
now I'm not entirely sure anymore what you think this module's usage is
intended to be like or maybe I'm just getting some implementation
details wrong, but I thought that it's a developer changing some bits of
a source file who triggers the compilation process (i.e. a daemon thread
will pick up those changes and issue compilation, isn't that the case?)?
There's no user (user != developer) involved in the whole process at
all, is there? Hence the only race condition that I can see is like what
happens if two or more developers edit the same source file, and I doubt
you want to even bear that race condition in mind.
Even if it's the user who triggers the compilation process (i.e. this
case assumes you only recompile changed source files on demand), I think
you don't have to worry about file locking as long as you synchronize
the compiler usage. Nonetheless I still doubt that it's the user who
triggers that, so that's just hypothetical and irrelevant nonsense anyway.
regards,
Bernhard
Werner Punz wrote on 12/11/2009 03:28 PM (GMT):
Jan-Kees van Andel schrieb:
Yeah, so do I, but at work I have to use Windows (at least I have
Cygwin installed) and at home I also like to play recent games. ;-)
But if it's only a file separator issue, I can maybe fix it myself and
build from the sources. (and of course commit it)
Sorry for answering so late, but I had a hellish ride back from Zurich
, came home basically at 2h30 in the morning, in between I have seen
parts of Vienna I probably really would not have wanted to see, at
least not during the night.
Anyway back to the topic.
It is probably just a handful of file separator issues with backslashes
being used automatically by File.separator in Regexps. I only can guess
there as well, because I have not had time yet to look into it.
It is probably easily fixed by just using the commons-io Filenameutils
instead, but there is another issue regarding Windows yet,I also have
not set the mutexes in the compiler parts to avoid windows filelocking
if more than one user hits the server. This has the same reasons, I
know about it, but yet have not had time to fix it yet.
The multiuser area is the one I started the day before yesterday and
probably will be finalized around next week.
The reason for the Windows bugs, is simply that I develop on OSX (before
Linux),
due to the abundance of filelocking, and the windows issues are more or
less a pre alpha bugfixing thing. Getting all the features in I want
comes first before going into that bugfixing round.
Sorry for that, but there is only so much time I can dedicate to the
project ;-), so it is either nail down the bugs, send in the patches
or wait until I have fixed then, or simply use a vm for a quick testing
with a Linux image ;-)
Werner
