Web Form Flooder

Logged In: NO

You could probably avoid the need for locking at all if you
make the configuration permutable, much like Java's own
String class.
Make a config and or a filereader class and whenever you
spawn a new thread, pass a reference to this one instance
class on, thus removing the need to have file operation in
each instance.
I.e:
nextThread = new Instance(configClass, dataFileReaderClass);
then in Instance code:
form.data = dataFileReaderClass.getData("company");

This can cause a bit of overhead so you might want to do
some profiling.

As an end note, beware that declaring a function
as "synchronized" to threaded classes does not solve locking
issues alone, you need correct locking and thread.wait() to
ensure locking. Otherwise you still risk lost updates, dining
philosophers or dirty reads.

MERLiiN

Logged In: YES
user_id=913401

Need to implement threadsafe locking on file operations. This can
probably be handled by adding "synchronized" to method
declarations for the formflood properties class.

Thanks for catching this.

Logged In: YES
user_id=924512

The reason the nulldomains.txt part appears is because the
DataDir= entry gets wiped out.