DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
Refcards Trend Reports
Events Video Library
Refcards
Trend Reports

Events

View Events Video Library

Related

  • Beyond Fail-Safe: Designing Fail-Operational State Machines for Physical AI
  • Series (4/4): Toward a Shared Language Between Humans and Machines — Humans as Co-Creators: Ethics, Strategy, and the Future of a Shared Language
  • Series (3/4): Toward a Shared Language Between Humans and Machines — Quantum Language and the Limits of Simulation
  • Series (2/4): Toward a Shared Language Between Humans and Machines — From Multimodality to World Models: Teaching Machines to Experience

Trending

  • Multi-Scale Feature Learning in CNN and U-Net Architectures
  • A Deep Dive into Tracing Agentic Workflows (Part 1)
  • A Scalable Framework for Enterprise Salesforce Optimization: Turning Outcomes Into an Operating System
  • Exactly-Once Processing: Myth vs Reality
  1. DZone
  2. Data Engineering
  3. AI/ML
  4. Writing a simple named pipes server in C#

Writing a simple named pipes server in C#

By 
Gunnar Peipman user avatar
Gunnar Peipman
·
Mar. 10, 12 · Interview
Likes (0)
Comment
Save
Tweet
Share
30.9K Views

Join the DZone community and get the full member experience.

Join For Free

I solved a little problem last night when playing with named pipes. I created a named pipe that writes all output to a file. Named pipes are opened for all users on a single machine. In this post I will show you a simple class that works as a pipe server.

In .NET-based languages we can use the System.IO.Pipes namespace classes to work with named pipes. Here is my simple pipe server that writes all client output to file.

public class MyPipeServer
{
    public void Run()
    {
        var sid = new SecurityIdentifier(WellKnownSidType.WorldSid, null);
        var rule = new PipeAccessRule(sid, PipeAccessRights.ReadWrite, 
                                      AccessControlType.Allow);
        var sec = new PipeSecurity();
        sec.AddAccessRule(rule);
 
        using (NamedPipeServerStream pipeServer = new NamedPipeServerStream 
              ("testpipe",PipeDirection.InOut, 100, 
               PipeTransmissionMode.Byte, PipeOptions.None, 0, 0, sec))
        {
            pipeServer.WaitForConnection();
 
            var read = 0;
            var bytes = new byte[4096];
 
            using(var file=File.Open(@"c:\tmp\myfile.dat", FileMode.Create))
                while ((read = pipeServer.Read(bytes, 0, bytes.Length)) > 0)
                {
                    file.Write(bytes, 0, read);
                    file.Flush();
                }
        }
    }
} 

Real-life pipe scenarios are usually more complex but this simple class is good to get things running like they should be.

POST (HTTP) Machine

Published at DZone with permission of Gunnar Peipman. See the original article here.

Opinions expressed by DZone contributors are their own.

Related

  • Beyond Fail-Safe: Designing Fail-Operational State Machines for Physical AI
  • Series (4/4): Toward a Shared Language Between Humans and Machines — Humans as Co-Creators: Ethics, Strategy, and the Future of a Shared Language
  • Series (3/4): Toward a Shared Language Between Humans and Machines — Quantum Language and the Limits of Simulation
  • Series (2/4): Toward a Shared Language Between Humans and Machines — From Multimodality to World Models: Teaching Machines to Experience

Partner Resources

×

Comments

The likes didn't load as expected. Please refresh the page and try again.

  • RSS
  • X
  • Facebook

ABOUT US

  • About DZone
  • Support and feedback
  • Community research

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Core Program
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 3343 Perimeter Hill Drive
  • Suite 215
  • Nashville, TN 37211
  • [email protected]

Let's be friends:

  • RSS
  • X
  • Facebook