summaryrefslogtreecommitdiffstats
path: root/server
Commit message (Collapse)AuthorAgeFilesLines
...
* server/red_worker: introduce an outgoing struct around out_bytes_counterAlon Levy2011-02-111-4/+6
|
* server/red_worker: renames to add channel_ prefix and consistent sigAlon Levy2011-02-111-20/+21
| | | | | | | | s/disconnect_channel_proc/channel_disconnect_proc/ s/release_item_proc/channel_release_pipe_item_proc/ s/handle_message_proc/channel_handle_parsed_proc/ Adds RedChannel* channel as first parameter to hold_pipe_item_proc
* server/red_worker: split cursor_channel_send_itemAlon Levy2011-02-111-42/+45
| | | | Split from cursor_channel_push
* server/red_worker: use red_channel begin_send_messageAlon Levy2011-02-111-12/+12
| | | | s/red_begin_send_message/red_channel_begin_send_message/
* server/red_worker: add red_channel_init_send_dataAlon Levy2011-02-111-87/+84
| | | | | Changes semantics of send to always hold/release regardless of block, like red_channel. A hold is just a reference count increment or nop.
* server/red_worker: split display_channel_send_itemAlon Levy2011-02-111-88/+94
| | | | Split it out of display_channel_push.
* server/red_worker: extract common_release_pipe_item from red_pipe_clearAlon Levy2011-02-111-50/+56
|
* server/red_worker: use red_channel pipe add versionsAlon Levy2011-02-111-16/+16
| | | | | s/red_pipe_add/red_channel_pipe_add/ s/red_pipe_add_after/red_channel_pipe_add_after/
* server/red_worker: shorten some lines using alias variablesAlon Levy2011-02-111-15/+23
|
* server/red_worker: introduce CommonChannelAlon Levy2011-02-113-182/+222
| | | | | | | 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.
* server/red_worker: use ack_data structAlon Levy2011-02-111-18/+20
| | | | start of move to red_channel based channels
* server/red_worker: change hold_item sig, drop the void*Alon Levy2011-02-111-4/+4
| | | | changed to PipeItem *
* server/smartcard: don't push our own error on reader addAlon Levy2011-02-091-3/+3
| | | | | | | | | | | | | | The device already sends one. There are actually two connections going on: server to client - this is the smartcard channel, it reuses the VSC protocol. server to device - this is an internal connection using VSC too. We generally just passthrough all messages from the client to the device, and from the device to the client. We only rewrite the reader_id because the device knows about a single id (it is actually a card id), and we may manage more then one in the future. Bottom line is that there was an extra VSC_Error message reaching the client.
* server/smartcard: ignore VSC_Init from clientAlon Levy2011-02-071-0/+3
|
* server/smartcard: print instead of assert on bad reader_id in ↵Alon Levy2011-02-071-1/+3
| | | | smartcard_char_device_on_message_from_device
* server/smartcard: libcacard uses network byte order, so we must tooAlon Levy2011-02-071-6/+19
|
* server/smartcard: libcacard removed ReaderAddResponseAlon Levy2011-02-071-42/+4
|
* server/smartcard: s/reader_id_t/uint32_t/ (libcacard changed)Alon Levy2011-02-071-6/+6
|
* server/red_channel: style fix in red_channel_init_send_dataAlon Levy2011-02-071-2/+2
|
* server/red_channel: red_channel_pipe_clear: assert on NULL channelAlon Levy2011-02-071-1/+2
|
* server/red_channel: add TODOAlon Levy2011-02-071-0/+4
|
* server/red_channel: export red_channel_sendAlon Levy2011-02-072-1/+2
|
* server/red_channel: add red_channel_waiting_for_ackAlon Levy2011-02-071-4/+7
| | | | small inline function to have the ack window logic.
* server/red_channel: protect red_channel_push from NULLAlon Levy2011-02-071-0/+4
|
* server/red_channel: reset pipe_size on clear (from red_worker)Alon Levy2011-02-071-0/+1
|
* server/red_channel: red_channel_event: push on blockedAlon Levy2011-02-071-1/+6
| | | | | | | try to push either on signal (write available) or when blocked and read signaled. From red_worker, copied for compatibility when switching later to RedChannel in red_worker. Doesn't make a lot of sense (but works), see comment in patch.
* server/red_channel: use red_channel_receiveAlon Levy2011-02-071-1/+1
|
* server/red_channel: add empty handle of SPICE_MSGC_DISCONNECTINGAlon Levy2011-02-071-0/+2
| | | | Simply ignored in red_channel_handle_message
* server/red_channel: add red_channel_receive (for red_worker)Alon Levy2011-02-072-0/+13
|
* server/red_channel: unstatic red_channel_pipe_clear (for red_worker)Alon Levy2011-02-072-2/+5
|
* server/red_channel: unstatic red_channel_push (for red_worker)Alon Levy2011-02-072-2/+7
|
* server/red_channel: two 80 column fixesAlon Levy2011-02-071-4/+6
|
* server/red_channel: add public red_channel_default_peer_on_errorAlon Levy2011-02-072-5/+5
| | | | for later use in red_worker
* server/red_channel: add red_channel_pipe_add_after (from red_worker)Alon Levy2011-02-072-0/+11
|
* server/red_channel: make client ack window configurableAlon Levy2011-02-072-2/+5
| | | | from red_worker
* server/red_channel (tunnel): change sig of red_channel_handle_messageAlon Levy2011-02-073-8/+11
| | | | for later usage with red_worker
* server/red_channel: make MAX_SEND_VEC 100Alon Levy2011-02-071-1/+1
| | | | | | | | MAX_SEND_VEC was 100 for DisplayChannel's RedChannel implementation which is being replaced with RedChannel in red_channel. So changing from 50 to 100 in red_channel (make this configurble?) - effectively increased memory usage by: (100-50)*sizeof(iovec)*(num_of_channels-2) ==(arch 64bit) 50*16*6 ~ 5k Not terrible.
* server/red_channel: reflect SpiceDataHeader fields in handle_parsed_procAlon Levy2011-02-073-4/+4
|
* server/red_channel: add red_channel_pipe_add_pushAlon Levy2011-02-075-24/+32
|
* server/red_channel: add hold_item (from red_worker)Alon Levy2011-02-077-9/+41
| | | | | | | | | | | | | hold_item called on init_send_data, matching release. This is not the behavior of red_worker - we ref++ (==hold_item) when sending the item, and --refs when releasing it, instead of only holding if the send is blocked. Note 1: Naming: hold_pipe_item is the proc name, the variable is called hold_item, this is similar to release_item/release_pipe_item naming. Note 2: All channels have empty implementation, we later use this when red_worker get's RedChannelized.
* server/red_channel: add out_bytes_counter (unused)Alon Levy2011-02-072-0/+6
|
* server/red_worker: fix used but uninitialized warning (gcc 4.6.0)Alon Levy2011-02-071-1/+1
|
* client/server: warning fixes (gcc 4.6.0)Alon Levy2011-01-254-19/+6
| | | | | gcc 4.6.0 added "[-Werror=unused-but-set-variable]", this and the next few fixes tend to that. Mostly harmless.
* client/server: add missing USE_TUNNELAlon Levy2011-01-251-0/+2
| | | | | disable some code that only makes sense when USE_TUNNEL is defined in client and server channel security level setting.
* client/server: add missing smartchannel channel security handlingAlon Levy2011-01-251-0/+3
| | | | | The name to channel id mapping for the smartcard channel is missing, add it in client and server.
* Update license header for server/red_parse_qxl.cHans de Goede2011-01-211-6/+6
| | | | This one mistakenly had a GPL header rather then an LGPL header.
* server/red_channel: fix segfault on red_channel_destroy if peer already removedAlon Levy2011-01-161-1/+1
|
* server/inputs_channel: use outgoing marshaller in red_channel/RedChannelAlon Levy2011-01-161-58/+76
|
* server/main_channel: use red_channel (most code is pipe send/marshall ↵Alon Levy2011-01-151-337/+441
| | | | separation)
* server/red_channel: no need for extra loopAlon Levy2011-01-151-1/+1
|
generated by cgit (git 2.34.1) at 2025-10-01 20:39:25 +0000