Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

named pipes for win32 #1150

Closed
totaam opened this issue Mar 25, 2016 · 3 comments
Closed

named pipes for win32 #1150

totaam opened this issue Mar 25, 2016 · 3 comments

Comments

@totaam
Copy link
Collaborator

totaam commented Mar 25, 2016

Split from #389 where an old patch can be found.

@totaam
Copy link
Collaborator Author

totaam commented Mar 25, 2016

Mostly done in r12219:

  • xpra list works
  • xpra version / info sort-of-work

TODO:

  • the client sometimes exits before processing the packet because the pipe has been closed by the server - this should be handled as an EOF instead
  • use the "socket-dir" as named pipe path? (currently hard-coded to Xpra\)
  • use the "socket-dirs" as the list of named pipe paths we search?
  • shadow server crashes easily with debug logging (could be the same issue as win32 shadow server crashes with bind-tcp and -d sound,gstreamer #1149)

@totaam
Copy link
Collaborator Author

totaam commented Apr 18, 2016

2016-04-18 10:29:47: antoine uploaded file named-pipes-mess.patch (6.9 KiB)

experimenting with tweaks to make named pipes work properly - hard

@totaam
Copy link
Collaborator Author

totaam commented Apr 18, 2016

This will do for 0.17, will follow up in #1174.

As it is, we can start a server and query it, ie:

xpra_cmd shadow

From another window:

xpra_cmd info

(or xpra_cmd version, etc..)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant