On Mon, Feb 04, 2002 at 05:30:35PM +0100, Stefan Bodewig wrote: > On Mon, 4 Feb 2002, Scott Sanders <[EMAIL PROTECTED]> wrote: > > > So, I only need to watch messages, and put them in the right task? > > Well, yes. Each message comes with the task instance as part of the > BuildEvent, so you can pile the messages up on a task by task basis > (this is what the current XmlLogger does AFAIK). >
Cool. Well building up a string on a task by task basis is still less memory-consuming than DOM. I will give it a try. > > Is the parallel task logged somehow? > > It is a built-in task starting with Ant 1.4. But it is just one > implementation of the more general TaskContainer concept and nobody > would stop people from writing their own task containers that invoked > other tasks in parallel as well. > What I meant was, if I see the taskStarted() come by and it was the parallel task, could I become 'parallel-aware' then, and then default back to the single-threaded, less consuming model after taskFinished()? > > Would I know that something is being paralleled? > > No, even the tasks themselves usually don't know that. > I understand the tasks don't, but can I as the logger or the container know? Thanks a lot Stefan. I will work on this. > Stefan > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > -- Scott Sanders - [EMAIL PROTECTED] -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
