Piping output of application A to application B

[vinay]

Hi All,

I have a very basic question on Windows CE regarding the usage of pipes.

I searched through net and didn't find any satisfactory answer.
Request you to please advice.

I have an application Say A and another application B. Now i want to pipe
the output A to B. This works both in Linux and Windows XP as follows.
$> A | B
The above command pipes output of A to B.
The same thing i want to try in WinCE and not sure how to do it.

Basically my 'A' application will write a buffer to 'stdout' and the 'B'
application will read from the 'stdin' into a buffer. This i checked both in
Linux and windows XP by running the command $> A| B on command prompt and it
works fine.

Please suggest me, how should i get this working in WinCE?

thanks a lot

[Ulrich Eckhardt]

vinay wrote:
> I have an application Say A and another application B. Now i want to pipe
> the output A to B. This works both in Linux and Windows XP as follows.
> $> A | B
> The above command pipes output of A to B.
> The same thing i want to try in WinCE and not sure how to do it.

Open a command prompt (cmd.exe) and try it. If that doesn't work, you will
need a different command prompt because such functions are part thereof.

Uli

--
Sator Laser GmbH
Geschäftsführer: Thorsten Föcking, Amtsgericht Hamburg HR B62 932

[Bruce Eitman [eMVP]]

Of course that assumes that the OP's system includes a command window.

--
Bruce Eitman (eMVP)
Senior Engineer
Bruce.Eitman AT EuroTech DOT com
My BLOG http://geekswithblogs.net/bruceeitman

EuroTech Inc.
www.EuroTech.com

"Ulrich Eckhardt" <eckh...@satorlaser.com> wrote in message
news:nhb1j6-...@satorlaser.homedns.org...

> vinay wrote:
>> I have an application Say A and another application B. Now i want to pipe
>> the output A to B. This works both in Linux and Windows XP as follows.
>> $> A | B
>> The above command pipes output of A to B.
>> The same thing i want to try in WinCE and not sure how to do it.
>
> Open a command prompt (cmd.exe) and try it. If that doesn't work, you will
> need a different command prompt because such functions are part thereof.
>
> Uli
>
> --
> Sator Laser GmbH

> Gesch�ftsf�hrer: Thorsten F�cking, Amtsgericht Hamburg HR B62 932

[vinay]

Hi,

Thanks for the answers.

I do have the cmd.exe in my WinCE image. I tried running the command
> A | B on WinCE command prompt, only the first application runs and the second application will never run!.

I'm running WinCE 6.0 on a ARM target.

Please suggest.

thanks

"Bruce Eitman [eMVP]" wrote:

> > Geschäftsführer: Thorsten Föcking, Amtsgericht Hamburg HR B62 932
>
>
>

[Bruce Eitman [eMVP]]

Okay, so let's assume that pipes are not implemented for Windows CE. That
would be reasonable since it isn't really needed for most Windows programs,
so Microsoft might have left the overhead of the feature out of the OS.

What is the real problem that you are trying to solve with this
implementation? Knowing what the real problem is might lead us to
suggestions that could solve it.

--
Bruce Eitman (eMVP)
Senior Engineer
Bruce.Eitman AT EuroTech DOT com
My BLOG http://geekswithblogs.net/bruceeitman

EuroTech Inc.
www.EuroTech.com

"vinay" <vi...@discussions.microsoft.com> wrote in message
news:3D131830-6C0B-4945...@microsoft.com...

>> > Gesch�ftsf�hrer: Thorsten F�cking, Amtsgericht Hamburg HR B62 932
>>
>>
>>

[vinay]

Hi Bruce,

I'm trying to Stream mpeg4 encoded video using RTSP server. I have an
application(say App A) which captures and encodes video. I'm writing this
encoded video to 'stdout'. I'm trying to pipe this to RTSP server (say App B)
which reads from 'stdin'.

The mpeg4 encoder is one application and the RTSP server is the other
application.

If winCE doesn't support pipes then i will have look for some alternate
options such as sockets etc.

The RTSP server framework upfront supports reading from a 'stdin' and hence
i was trying this option.

please Suggest if there are others ways to achieve this, apart from sockets.

thanks

"Bruce Eitman [eMVP]" wrote:

> >> > Geschäftsführer: Thorsten Föcking, Amtsgericht Hamburg HR B62 932
> >>
> >>
> >>
>
>
>

[Christopher Fairbairn [MVP]]

Hi,

"vinay" <vi...@discussions.microsoft.com> wrote in message

news:E0DAC7FB-9495-4ED6...@microsoft.com...

> I'm trying to Stream mpeg4 encoded video using RTSP server. I have an
> application(say App A) which captures and encodes video. I'm writing this
> encoded video to 'stdout'. I'm trying to pipe this to RTSP server (say App
> B)
> which reads from 'stdin'.

Rather than a UNIX pipes based implementation model, could you instead
repackage or architecture your code to allow the mpeg4 encoding logic to be
used as a library by the RTSP server?

I imagine instead of writing to stdout that the mpeg4 encoder could call
into a callback function provided by the RTSP server (or the RTSP server
could pull data from the encoder) as data became available.

If you want to be able to deploy/upgrade components seperatly you could
package the mpeg4 encoder as a dynamic link library (*.dll), otherwise it
could even be a static lib that was compiled into the server application
during link time.

If you were worried about coupling the two components, you could always
define the interface between the encoder and server in generic terms, to
allow you to swap and replace components such as other audio/video codecs as
desired.

This way you only have one executable and process to deal with. It should
lead less syncronisation or stuck/dead process issues, and a simplified
development model.

Hope this helps,
Christopher Fairbairn