summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
...
* server: add reds_stream_{read,write,free,remove_watch}()Marc-André Lureau2011-02-275-10/+80
| | | | https://bugs.freedesktop.org/show_bug.cgi?id=34795
* server: s/RedsStreamContext/RedsStreamMarc-André Lureau2011-02-2711-47/+47
| | | | https://bugs.freedesktop.org/show_bug.cgi?id=34795
* server/reds: remove unused readvMarc-André Lureau2011-02-272-3/+0
| | | | | | Let's not bother with it since nobody uses it, and it's not implemented for SSL anyway https://bugs.freedesktop.org/show_bug.cgi?id=34795
* build: make it silentMarc-André Lureau2011-02-272-3/+5
| | | | | | | | | | | This patch make it easier to spot warnings in compilation. It should work with older versions of automake that don't support silent rules. If you want verbose build, make V=1. Signed-off-by: Uri Lublin <uril@redhat.com> https://bugs.freedesktop.org/show_bug.cgi?id=34795
* client/windows: use SPICE_PROTOCOL_DIR in project include dirsArnon Gilboa2011-02-131-4/+4
| | | | | | | | | instead of ..\..\..\spice-protocol. Relative path to another git tree is a bit ugly, since it requires spice-protocol to be in a specific location. SPICE_PROTOCOL_DIR should also be used in windows qxl and vdagent instead of SPICE_COMMON_DIR, which is an old and confusing name, due to the common directory in spice git repo.
* server/tests/basic_event_loop: fix bzero warningAlon Levy2011-02-111-0/+1
|
* tests/migrate.py: refactor to allow importing for later useAlon Levy2011-02-111-51/+81
|
* Drop static_title.bmp from windows/Makefile.amHans de Goede2011-02-111-1/+0
|
* server/red_worker: cursor_channel_send_item: don't downcastAlon Levy2011-02-111-3/+5
|
* server/red_worker: match channel_release_pipe_item_proc to red_channelAlon Levy2011-02-111-9/+10
|
* 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 *
* update required minimal libcacard to 0.1.2Alon Levy2011-02-091-1/+1
|
* client/smartcard: libcacard dropped ReaderAddResponseAlon Levy2011-02-092-18/+78
| | | | | | | | | | | | uses VSC_Error with code==VSC_SUCCESS instead. This means that the VSC_Error message is overloaded. Instead of the other option of adding a message id, since the connection is TCP so no messages may be dropped or reordered, by having each message followed by a response there is no ambiguity. Still this commit adds a queue for messages that we only have one of which outstanding at a time, i.e. send, wait for response, send the next, etc. This further simplifies the logic, while not adding much overhead since only when spicec starts up it has a situation where it needs to send two events (ReaderAdd and ATR for Card Insert).
* 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.
* client/smartcard: ignore VSC_InitAlon Levy2011-02-071-0/+2
|
* 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
|
* client/smartcard: s/reader_id_t/uint32_t/ (libcacard changed)Alon Levy2011-02-072-11/+11
|
* 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
generated by cgit (git 2.34.1) at 2025-10-03 04:20:30 +0000