hi,
Jan: I can see your point, but with huge projects in which the final
artifacts are converted to exe's with a tool like Excelsior Jet, that
would not be an option. This is the same scenario where I am in right now.
Stefan: Yes - the copy task would be a poor example ie the presence of
an optional parallel within that task would have very limited/specific
uses. But I think, based on my current project, that it would definitely
be useful in the scp and ftp tasks.
Do you agree?
thanks,
Vijay
[EMAIL PROTECTED] wrote:
Consider the scenario where the file transfer takes a long time:
would it be a good idea to have the copy/scp/ftp tasks create
different threads for each file?
There is no built-in support for anything like this in Ant, no.
I could imagine that we'd add a patch that enabled optional (on
user-demand) parallel behavior for these tasks. Personally I see the
point for the network transfer kind of tasks, but wouldn't want it on
copy, but that may be my experience with a very slow disk in my
notebook.
At first step for improving performance I would think about skipping
things.
Why to try to upload a lot of files which havent changed and are already
there?
In that case:
<scp><fileset><modified>
Jan
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
