summaryrefslogtreecommitdiffstats
path: root/server/red_client_cache.h
Commit message (Collapse)AuthorAgeFilesLines
* Use the spice-common logging functionsMarc-André Lureau2012-03-251-2/+2
| | | | | It will abort by default for critical level messages. That behaviour can be tuned at runtime.
* server/red_worker: multiple client support - base splitAlon Levy2011-08-231-26/+26
| | | | | | | | | | | | | | | | | | This patch compiles but breaks spice. Split both display and cursor channels to a client part and channel part. Introduce DisplayChannelClient, CursorChannelClient, CommonChannelClient. don't disconnect channel on client disconnect. Move all caches to the ChannelClient's. Remove reference counting of the channel. No new functionality introduced. NOTE: Introduces a crash in disconnections, a regression, resulting from incorrect thread access, that is fixed in the patch titled: "server: registering RedChannel in reds, instead of Channel"
* server: move pipe from RedChannel to RedChannelClientAlon Levy2011-08-231-5/+11
| | | | | | | | | | | | | | | | | | | | | | | Another cleanup patch, no change to behavior (still one client, and it disconnects previous client if any). The implementation for multiple client is straightforward: the pipe remains per (channel,client) pair, so it needs to move from the RedChannel that to RedChannelClient. Implementation using a single pipe with multiple consumers (to reflect different latencies) doesn't fit well with pipe rewriting that is used by the display channel. Additionally this approach is much simpler to verify. Lastly it doesn't add considerable overhead (but see the display channel changes in a later patch for a real place to rethink). This patch is just technical, changing signatures to reflect the first argument (oop style) so red_channel becomes red_channel_client. Some places may seem odd but they should be fixed with later comits where the channels grow to support multiple clients. Sound (playback/record) channels are the only ones not touched - this is consistent with previous patches, since they have been left out of the RedChannel refactoring. That is left as future work. (note that they don't use a pipe, which was the reason for not refactoring).
* server/red_worker: drop red_pipe_add_tail, use red_channel_pipe_add_tailAlon Levy2011-08-231-1/+1
| | | | | | The only difference between them being that the later also does a push. I don't believe that to be a problem, but if it does I can always introduce a push'less version.
* server/red_worker: use red_channel_pipe_item_initAlon Levy2011-03-021-1/+1
| | | | replaces in file red_pipe_item_init.
* server/red_worker: introduce CommonChannelAlon Levy2011-02-111-1/+1
| | | | | | | with everything (almost) not in red_channel's RedChannel As a result of CommonChannel a free cb is added to EventHandler, to take care of non zero offset for embedded EventHandler.
* Relicense everything from GPL to LGPL 2.1+Alexander Larsson2010-04-131-9/+9
|
* Use spice allocator in server/Alexander Larsson2010-03-111-4/+1
|
* Rename symbols that were changed in spice-protocolAlexander Larsson2010-02-041-2/+2
| | | | | | This is an automatic change using: $ find -name "*.[ch]" | xargs ../spice-protocol/rename-identifiers.sh ../spice-protocol/renames $ find -name "*.cpp" | xargs ../spice-protocol/rename-identifiers.sh ../spice-protocol/renames
* fresh startYaniv Kamay2009-10-141-0/+136