diff options
author | Alon Levy <alevy@redhat.com> | 2011-02-09 12:09:43 +0200 |
---|---|---|
committer | Alon Levy <alevy@redhat.com> | 2011-02-09 12:11:51 +0200 |
commit | 51da06793c33ff30b45154ccfc6e28d6d0d35db6 (patch) | |
tree | 1fb735d7e8d4826cb344640b79b4b7a7106bae6f /server/red_memslots.h | |
parent | 91bf99a1e98623905485089ff0b7886e30c369a4 (diff) | |
download | spice-51da06793c33ff30b45154ccfc6e28d6d0d35db6.tar.gz spice-51da06793c33ff30b45154ccfc6e28d6d0d35db6.tar.xz spice-51da06793c33ff30b45154ccfc6e28d6d0d35db6.zip |
server/smartcard: don't push our own error on reader add
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.
Diffstat (limited to 'server/red_memslots.h')
0 files changed, 0 insertions, 0 deletions