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 client capabilities flags to server source #169

Closed
totaam opened this issue Jul 31, 2012 · 7 comments
Closed

move client capabilities flags to server source #169

totaam opened this issue Jul 31, 2012 · 7 comments

Comments

@totaam
Copy link
Collaborator

totaam commented Jul 31, 2012

Issue migrated from trac ticket # 169

component: core | priority: minor | resolution: fixed

2012-07-31 06:54:36: antoine created the issue


this will make it easier to support multiple clients and is the right place for them

@totaam
Copy link
Collaborator Author

totaam commented Aug 24, 2012

2012-08-24 18:00:39: antoine changed status from new to accepted

@totaam
Copy link
Collaborator Author

totaam commented Aug 24, 2012

2012-08-24 18:00:39: antoine changed title from move client capabilities flags to server source to move client capabilities flags to server source - support multiple clients

@totaam
Copy link
Collaborator Author

totaam commented Aug 24, 2012

2012-08-24 18:00:39: antoine commented


part1 done in r1365 (many details in changelog)

Now we can much more easily / think about:

  • move most of process_hello to ServerSource, mmap bits, flags, etc
  • move towards supporting many instances of ServerSource at once, each with a different protocol instance, with a way for clients to request damage data for themselves alone (will be tricky to avoid the acknowledge_changes only when needed..)
  • start thinking about how to handle map/configure events: ignore messages from slaves? focus applies. unmap should be forwarded to the others.. move/resize? these will be hard!
  • start thinking about sharing encoders/output: if two clients use the same video encoding... hard to do if we have varying framerates as we should!
  • identify each client, how? (for logging, xpra info, etc)
  • keyboard will be extremely difficult: if layouts are different, we need to set all of them (and run out of keycodes?), when keys are pressed/unpressed and conflict... what do we do?

@totaam
Copy link
Collaborator Author

totaam commented Aug 27, 2012

2012-08-27 19:03:45: antoine changed status from accepted to closed

@totaam
Copy link
Collaborator Author

totaam commented Aug 27, 2012

2012-08-27 19:03:45: antoine changed resolution from ** to fixed

@totaam
Copy link
Collaborator Author

totaam commented Aug 27, 2012

2012-08-27 19:03:45: antoine changed title from move client capabilities flags to server source - support multiple clients to move client capabilities flags to server source

@totaam
Copy link
Collaborator Author

totaam commented Aug 27, 2012

2012-08-27 19:03:45: antoine commented


More in r1407, this is enough for this ticket, will follow up in #41 which is the original ticket for "multiple clients".

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