Pipe name handling on client side about h.pipes HOT 9 CLOSED

This example is oversimplified by the way. I also removed \\.\pipe\ from all names to make .StartsWith() work.

from h.pipes.

In fact, I want to replace

var connectionPipeName = $"{PipeName}_{++NextPipeId}";

to

var connectionPipeName = $"{PipeName}_{Guid.NewGuid()}";

P.S. I released this change.

from h.pipes.

The library also contains PipeWatcher.GetActivePipes(), which contains the following code:

public static IReadOnlyCollection<string> GetActivePipes()
{
    return Directory
        .EnumerateFiles(@"\\.\pipe\")
        .Select(path => path.Replace(@"\\.\pipe\", string.Empty))
        .ToList();
}

But I do not recommend using pipe file enumeration in principle, it is very slow.

from h.pipes.

Regarding the problem with invalid characters, yes, EnumerateFiles returns such an exception when a path contains System.IO.Path.GetInvalidPathChars:

T:System.ArgumentException:
//     path is a zero-length string, contains only white space, or contains invalid
//     characters. You can query for invalid characters by using the System.IO.Path.GetInvalidPathChars
//     method. - or - searchPattern does not contain a valid pattern.

But as I said, EnumerateFiles is generally not good for keeping track of pipes, it is very slow.

from h.pipes.

At the moment I'm trying to figure out why you need to monitor active pipes at all?

from h.pipes.

I don't need all the pipes but I just need to have what server uses currently. I see that during operation I can have:

• pipename
• pipename_1
• pipename_2, etc.

But if the client only knows pipename, then client is unable to connect to the server when numbers are there. So, I had to find a pipe that starts with pipename. To solve this, I enumerated all the pipes and pick a suitable one with the code above. However, in case there are multiple pipes at the same time, it takes only the first one and it might be an incorrect one.

from h.pipes.

Ok, the problem is clear. I will add a Connection.PipeName property that will contain the currently used name.
The principle of the server is that there is a common pipe through which a unique pipeName is transmitted for each client, which is used for a direct connection with the client. Without this trick, only one client would be able to connect to the server. But, in fact, there is already a SingleConnectionPipeServer class that is optimized for a single connection.

from h.pipes.

I have released a new version. I removed the Connection.Id and Connection.Name properties because the Connection.PipeName will be unique.

from h.pipes.

That's a huge change. Thank you for quick reply. I'll try to use this one. And also will try SingleConnectionPipeServer, which seems to be the best way for my use case.

from h.pipes.