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

move websockify in the xpra process #1136

Closed
totaam opened this issue Feb 25, 2016 · 13 comments
Closed

move websockify in the xpra process #1136

totaam opened this issue Feb 25, 2016 · 13 comments

Comments

@totaam
Copy link
Collaborator

totaam commented Feb 25, 2016

Issue migrated from trac ticket # 1136

component: server | priority: major | resolution: fixed

2016-02-25 02:55:03: antoine created the issue


So we don't have to exec anything, then we also won't be needing the proxy instance running xpra side (which is forwarding to and from the websockify process, using 2 threads).
See also #1134.

@totaam
Copy link
Collaborator Author

totaam commented Mar 16, 2016

2016-03-16 06:14:47: antoine changed status from new to assigned

@totaam
Copy link
Collaborator Author

totaam commented May 24, 2016

2016-05-24 17:27:06: antoine uploaded file websockify-inprocess.patch (22.0 KiB)

move websockify handling in process

@totaam
Copy link
Collaborator Author

totaam commented May 24, 2016

2016-05-24 17:30:58: antoine commented


The patch above works fine, only left todo:

  • handle html=/path/to/www and generate / detect correct path (ie: on osx, in the app bundle)
  • TLS setup
  • man page updates
  • test tcp-proxy mode better
  • use the peek function to avoid creating a whole protocol instance (and threads) if the packet header is invalid
  • verify blocking sockets and timeout values

@totaam
Copy link
Collaborator Author

totaam commented May 26, 2016

2016-05-26 16:35:15: antoine commented


Mostly done in r12688. Firefox is still having problems, but that doesn't seem to be anything new.
Still todo:

  • TLS
  • bail out early on invalid packet header

@totaam
Copy link
Collaborator Author

totaam commented May 30, 2016

2016-05-30 13:04:47: antoine uploaded file web-ssl.patch (10.9 KiB)

attempts at preventing ssl from deadlocking - failed

@totaam
Copy link
Collaborator Author

totaam commented May 30, 2016

2016-05-30 13:11:28: antoine changed status from assigned to new

@totaam
Copy link
Collaborator Author

totaam commented May 30, 2016

2016-05-30 13:11:28: antoine changed owner from antoine to afarr

@totaam
Copy link
Collaborator Author

totaam commented May 30, 2016

2016-05-30 13:11:28: antoine commented



@afarr: the html client should be faster now

@totaam
Copy link
Collaborator Author

totaam commented Jun 24, 2016

2016-06-24 22:26:16: maxmylyn commented


HTML client is by far faster. It's like night and day faster now.

I'd say performance in Chrome is 90% as good as Python.

@totaam
Copy link
Collaborator Author

totaam commented Jun 24, 2016

2016-06-24 22:28:38: maxmylyn changed status from new to closed

@totaam
Copy link
Collaborator Author

totaam commented Jun 24, 2016

2016-06-24 22:28:38: maxmylyn set resolution to fixed

@totaam
Copy link
Collaborator Author

totaam commented Jun 24, 2016

2016-06-24 22:28:38: maxmylyn commented


Oh, sorry, I hit submit without thinking.

Closing.

@totaam totaam closed this as completed Jun 24, 2016
@totaam
Copy link
Collaborator Author

totaam commented Jul 12, 2016

2016-07-12 17:52:23: antoine commented


Milestone renamed

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