update license header text

Update the copyright year in all .c, .h and .xml files

Quiet warnings of POSIX deprecation in win32 support sources.

No functional Change: Removing trailing whitespace. This also means that "blank" lines consisting of just spaces or tabs are now really blank lines

No functional change: simple detabbing of indented code.

Update copyright year to 2005 and standardize on current copyright owner line.

fix name of The Apache Software Foundation

apply Apache License, Version 2.0

update license to 2004.

finished that boring job: update license to 2003. Happy New Year! ;-))

Add a timeout option to wintty. This allows the user to specify a number of seconds to wait after the program terminates before closing the window. Previously, the windows would remain open indefinately. This option is not currently being used by Apache.

Always using -t "Window Title" option myself, so I never caught this.

An absolutely unnecessary hack around MSVC emits that the symbol may not have been initialized. [Of course it was initialized, the same code protects both it's initialization and reset.]

Update our copyright for this year.

Significant cleanup and enable wintty to -always- escape from the service context when the run-as-user is LocalSystem or has access to the windows station and desktop. The original method did not give us a visible tty unless the 'Allow Service to Interact with Desktop' toggle was set.

Need broader permissions if we are to read and the set the flags that apply to the console stream.

Must admit, my use case was focused on services. It seems that if we had a console, we weren't reassigning stdhandles with AllocConsole(). Open the conin/conout very explicitly, and clean up some other cruft.

Eliminate emits

A bit more clarity, and that's it for now.

Clarify the wintty purpose and syntax. Still some todos: an option to just abort user feedback and close the window instantly upon loosing the stdin pipe, allow the stdin pipe to be tee'ed on win32, and still add some graceful error handling for a real-world deployment.

Q. "Why can't I watch my server's activity?" A. You can. This is a little tool I dreamed up while fighting a ton of battles on several fronts. It demonstrates that reliable piped logs on win32 still need work, that we launch log processes far too many times, and generally gives admins more blinky lights on win32. But it's too practial of an example to leave on my hard drive gathering dust. Note that the support/win32 will be used for really non-unix/non-portable applications. Perhaps something similiar would be useful all the way around, and perhaps some of this code can get into the apr core. But for this moment, it serves a purpose for beta development.