<?xml version="1.0" encoding="utf-8"?><rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"><channel>
	

	<title>OpenSourceList.org - WinPipe</title>
	<link>http://www.opensourcelist.org/</link>
	<description>WinPipe: This feed will update only when this entry is modified.</description>
	<pubDate>Wed, 20 Aug 2008  06:26:14 +0000</pubDate>
	<language>en</language>

<item>
    <title>WinPipe</title>
    <link>http://www.opensourcelist.org/software/770</link>
    <pubDate>Mon, 30 Jun 2008 14:44:35 EST</pubDate>
    <guid>http://www.opensourcelist.org/software/770/20080630144435</guid>
    <description>
Description:WinPipe is a combination of a utility and a dynamic link library which allows an application to spawn a child process with a wide range of abilities for manipulating the standard console handles of the child. The purpose of WinPipe was to overcome problems and limitations related to standard I/O redirection of Windows console applications.
Comments:The normal way of redirecting console input and output under MS Windows is explained by Microsoft in the article "Creating a Child Process with Redirected Input and Output." The method used by Microsoft is a call to the CreateProcess API function with the standard handles redirected to pipes.

There are several problems with this method. One problem is that many Windows Console API functions will not work properly when the console is redirected in this way. The standard windows console handles point to Console Screen Buffer and Console Input Buffer objects, a pipe will only function equivalently to these objects when passed to ReadFile, WriteFile, or PeekNamedPipe.

WinPipe solves these problems by creating an easy programming interface where the child process executes with access to real console handles, but the parent application can read from and write to the child console.</description>
<content:encoded><![CDATA[<div class="osl_software"><p>Software: <a href="http://www.micrognu.com/proj/nocost/wpipe/">WinPipe</a></p><p>Description: WinPipe is a combination of a utility and a dynamic link library which allows an application to spawn a child process with a wide range of abilities for manipulating the standard console handles of the child. The purpose of WinPipe was to overcome problems and limitations related to standard I/O redirection of Windows console applications. </p><p>Comment: The normal way of redirecting console input and output under MS Windows is explained by Microsoft in the article "Creating a Child Process with Redirected Input and Output." The method used by Microsoft is a call to the CreateProcess API function with the standard handles redirected to pipes.

There are several problems with this method. One problem is that many Windows Console API functions will not work properly when the console is redirected in this way. The standard windows console handles point to Console Screen Buffer and Console Input Buffer objects, a pipe will only function equivalently to these objects when passed to ReadFile, WriteFile, or PeekNamedPipe.

WinPipe solves these problems by creating an easy programming interface where the child process executes with access to real console handles, but the parent application can read from and write to the child console. </p><p>Added: 2008.06.30 (50 days ago)</p></div>
]]></content:encoded>
</item>
</channel>
</rss>
