Repository navigation
Change from gRPC to Named Pipes #374
Description
Today there is a need to install asp.net core in addition to .net core because of gRPC.
Also, inorder to communicate in a faster and better way between proccesses(IPC) of LogExpert we will change the communication from gPRC to Named Pipes.
gPRC will be used probably in a differnt part of the code(e.g. source of log) but not for the IPC purpose.
The reason choosing this was .net core support and cross platform.
Activity
[-]I am trying to improve the ipc(remove the grpc.core). I am trying to test the 1 instance(enable/disable) but can't seem to make it work. @Hirogen can you help? I am on the Devlopment branch. I get an exception on line 159 in `Program.cs` `client.NewWindowOrLockedWindow(new Grpc.FileNames { FileNames_ = { args } });` Exception: The SSL connection could not be established, see inner exception. InnerException: Cannot determine the frame size or a corrupted frame was received.[/-][+]Change from gRPC to Named Pipes[/+]Hirogen commentedon Apr 2, 2025
What is the USE CASE for InterProcess communications, why would I want to communicate between logexpert processes, is this really necessary?
RandallFlagg commentedon Apr 2, 2025
Same question I was asking my self from the begining. Since you are the project lead and owner I though you knew. :)
Luckaliy we have the code to answer your question.
LogExpert/src/LogexpertgRPCService/Protos/Logexpert.proto
Lines 10 to 20 in 8fba5b8
Hirogen commentedon Apr 3, 2025
yeah I implemented that, because that was in the old code, but I could never find a real use case where to use that.
RandallFlagg commentedon Apr 3, 2025
Maybe let's open it for discussion so people can say what they need from a multiple window/instance of LogExpert. The only one I can think of is to move tabs between windows.