ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rick Yazwinski <rick.yazwin...@solect.com>
Subject RE: [PATCH] multithreading tasks
Date Thu, 22 Jun 2000 18:19:59 GMT
Did I miss the XML example? :(  Is there an archive?  Conor, can you send it
again?

Looking at James' reply I kinda get the feel for the build.xml.  I have to
admit that I was thinking something more like:
	<async name="task1" host="machine1">
		<task... />
		<task... />
		etc...
	</async>
	<async name="task2">
		<task... />
		<task... />
		etc...
	</async>

With the ability to do something like:
	<join tasks="task1, task2" />
and potientially some other niceties like:
	<syncronize tasks="task1, task2" />
to get the threads created and blocked at an initialized, but not active
state...

Maybe this is too much for ant, but it could be cool ;)

	Rick...

> -----Original Message-----
> From: James Duncan Davidson [mailto:james.davidson@eng.sun.com]
> Sent: Thursday, June 22, 2000 2:01 PM
> To: ant-dev@jakarta.apache.org
> Subject: Re: [PATCH] multithreading tasks
> 
> 
> on 2000/06/22 04:22, Conor MacNeill at 
> conor@cortexebusiness.com.au wrote:
> 
> Thanks for the XML sample. This helps a lot!
> 
> > <target name="test" depends="install, testcode">
> > <wlrun taskname="server" async="yes"
> > classpath="${weblogic.boot.classpath}"
> > wlclasspath="${weblogic.classes}:..."
> > name="${server.name}" home="${weblogic.home}"
> > properties="${server.name}/${server.name}.properties"/>
> 
> Ok.. So I don't have any problem with the async flag being an 
> attribute on a
> task. Seems about right.
> 
> > <sleep delay="80000"/>
> 
> Yeah, sure it can be a task. But if this is telling the 
> acutal Ant runtime
> to pause for a while, how about a PI?
> 
> <?pause interval="880000"?>
> 
> Don't know if it's any better though. Especially since the 
> async is an XML
> attrib. Besides, a sleep task can just spin. On balance, I'm split.
> 
> > <echo message="starting JUnit test"/>
> > <java taskname="junit"
> > fork="yes"
> > classpath="${testrun.classpath}"
> > classname="AllTests"/>
> > <wlstop classpath="${weblogic.classes}"
> > user="..."
> > password="..."
> > url="..." />
> > <join/>
> 
> Once again, since this is flow control, maybe a PI? Would the 
> join task look
> for the thread that was started? Are all asynch threads 
> registered somewhere
> in the project?
> 
> > <echo message="test finished"/>
> > </target>
> 
> Hmmm... Warming... I guess I don't have an issue with doing 
> acutal threading
> if it's something like this... I'm really wanting to see us 
> hit a useful and
> simple way of expressing it if we are going to do it.
> 
> If you look at PI's and decide that I'm smoking dope, then go 
> ahead with
> what you've got, I'll remove my -1.
> 
> .duncan
> 

Mime
View raw message