|
From: Leif M. <le...@ta...> - 2006-02-10 15:03:41
|
Daniel,
You are quite welcome. It is already all checked in for the 3.2.0
release. I will leave
the default value false for now until it has been tested more and I am
sure that it does not
have any adverse effects on performance on any platforms.
Be sure to upgrade as soon as the release is out.
Cheers,
Leif
Daniel Mace wrote:
> Leif,
>
> IT WORKS! Awesome. :)
>
> Will this feature/workaround be going into the next release? I'll be
> using this snapshot in the meantime.
>
> It's been a pleasure working on this with you. Many thanks. If there are
> any more specific details you need from me regarding this problem, I'd
> be glad to help.
>
> Thanks again.
>
> Daniel Mace
> Software Engineer, Payroll Integration
> benefitfocus.com
> 843-849-7476 x393
>
>
>
>> -----Original Message-----
>> From: wra...@li...
>> [mailto:wra...@li...] On Behalf
>> Of Leif Mortenson
>> Sent: Friday, February 10, 2006 9:43 AM
>> To: wra...@li...
>> Subject: Re: [Wrapper-user] Wrapper stdout redirection in realtime
>>
>> That link should have been:
>> http://wrapper.tanukisoftware.org/tmp/3.2.0-e/wrapper-windows-
>> x86-32-3.2.0-e.zip
>>
>> Leif Mortenson wrote:
>>
>>> Daniel,
>>> It is possible to explicitly flush stdout by calling
>>> fflush(stdout). I added a new wrapper.console.flush=true property,
>>> which when set to true will do this after
>>> each line of output logged to the console. Could you try out the
>>> snapshot below
>>> with and without the above property and let me know if it makes any
>>> difference.
>>> When using the wrapper in normal operation, it doesn't seem to do
>>> anything at all. The performance tests are unaffected one
>>>
>> way or the
>>
>>> other. That may be because the command prompt is causing
>>>
>> an automatic
>>
>>> flush or something.
>>>
>>>
>>>
>> http://wrapper.tanukisoftware.org/tmp/3.1.2-d/wrapper-windows-x86-32-3
>>
>>> .2.0-e.zip
>>>
>>>
>>> Cheers,
>>> Leif
|