#169 closed task (fixed)
move client capabilities flags to server source
Reported by: | Antoine Martin | Owned by: | Antoine Martin |
---|---|---|---|
Priority: | minor | Milestone: | 0.6 |
Component: | core | Version: | trunk |
Keywords: | Cc: |
Description
this will make it easier to support multiple clients and is the right place for them
Change History (3)
comment:1 Changed 10 years ago by
Status: | new → accepted |
---|---|
Summary: | move client capabilities flags to server source → move client capabilities flags to server source - support multiple clients |
comment:2 Changed 10 years ago by
Resolution: | → fixed |
---|---|
Status: | accepted → closed |
Summary: | move client capabilities flags to server source - support multiple clients → move client capabilities flags to server source |
comment:3 Changed 17 months ago by
this ticket has been moved to: https://github.com/Xpra-org/xpra/issues/169
Note: See
TracTickets for help on using
tickets.
part1 done in r1365 (many details in changelog)
Now we can much more easily / think about:
process_hello
toServerSource
, mmap bits, flags, etcServerSource
at once, each with a differentprotocol
instance, with a way for clients to request damage data for themselves alone (will be tricky to avoid theacknowledge_changes
only when needed..)