summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* fix for not reseting client palette caches on migrationYonit Halperin2010-06-211-0/+2
|
* Lossy compression of RGBA images (on WAN connection)Yonit Halperin2010-06-215-33/+238
| | | | | The RGB channels are compressed using JPEG. The alpha channel is compressed using LZ.
* applying zlib compression over glz on WAN connectionYonit Halperin2010-06-2123-31/+504
|
* Make opengl optional, disabled by defaultAlexander Larsson2010-06-2114-55/+137
| | | | | | | | | | The OpenGL renderer isn't really useful right now, its not quite up to date, its not really faster than software and it only supports a limited subset of drivers. So, lets disable it for now. Long term opengl rendering of the 2d part of spice is important if we want to combine 2d and 3d rendering (say if spice adds opengl support in the protocol). But until then this is isn't useful for normal use.
* Make generated marshallers build on win32Alexander Larsson2010-06-185-8/+30
|
* Add server/demarshaller.hAlexander Larsson2010-06-181-0/+25
|
* Make sound data @as_ptr to avoid copying dataAlexander Larsson2010-06-184-11/+13
|
* Make ping data @as_ptr to avoid copying dataAlexander Larsson2010-06-182-1/+3
|
* Make cursor data @as_ptr to avoid copying dataAlexander Larsson2010-06-184-7/+8
|
* Support @as_ptr in demarshaller to avoid copying data unnecessaryAlexander Larsson2010-06-181-1/+13
|
* Make pointer types in messages be 64bit in memoryAlexander Larsson2010-06-181-2/+2
| | | | | | | | Right now we always assume pointers are stored as SPICE_ADDRESS, i.e. 64bit, independent on the size sent on the network. This is required for 64bit architectures of course, but slightly overkill on 32bit architectures, so needs fixing when all SPICE_ADDRESS elements can be made internal.
* Don't pack the message structuresAlexander Larsson2010-06-181-87/+83
|
* Make all message structs internal to spiceAlexander Larsson2010-06-187-7/+504
| | | | | | | We move all message structs from spice-protocol to spice as we want to be able to change these as needed internally. The on-network format is no longer defined by these structures anyway, but rather by the spice protocol description.
* Allow multiple --include argsAlexander Larsson2010-06-181-3/+4
|
* Use generated demarshallers in serverAlexander Larsson2010-06-183-73/+118
|
* Generate demarshallers on server sideAlexander Larsson2010-06-181-1/+5
|
* Make tunnel_service_add members be of cstring array sizeAlexander Larsson2010-06-181-2/+2
|
* Switch client to use generated marshallersAlexander Larsson2010-06-1810-167/+219
|
* Generate and link marshallers into clientAlexander Larsson2010-06-183-1/+37
|
* Re-enable cache freeingAlexander Larsson2010-06-181-1/+1
| | | | I don't know why this was disabled but it seems like a bad idea
* Convert reds.c to use SpiceMarshallerAlexander Larsson2010-06-181-302/+211
|
* Convert snd_worker.c to use SpiceMarshaller and generated marshallersAlexander Larsson2010-06-181-145/+94
|
* Convert red_worker.c to use SpiceMarshaller for marshallingAlexander Larsson2010-06-181-781/+997
|
* Generate marshallers in serverAlexander Larsson2010-06-181-0/+13
|
* Use @ptr32 for 32bit offsets in spice.protoAlexander Larsson2010-06-181-2/+2
|
* Add @nomarshal in a few places where we're marshalling manuallyAlexander Larsson2010-06-181-11/+11
|
* spice.proto: add @outvar markupAlexander Larsson2010-06-181-15/+15
| | | | With this we can reference pointer member with no naming conflicts
* Add support for generating message and structure marshallersAlexander Larsson2010-06-182-1/+392
|
* Add SpiceMarshaller for easy marshallingAlexander Larsson2010-06-184-0/+649
|
* Generate demarshalling code on win32 tooAlexander Larsson2010-06-181-13/+50
|
* Client: Use the autogenerated demarshallersAlexander Larsson2010-06-1820-450/+235
| | | | | | | | | | | | | | | | When a message has been read from the network we now pass it into the generated demarshaller for the channel. The demarshaller converts the network data to in-memory structures that is passed on to the spice internals. Additionally it also: * Converts endianness * Validates sizes of message and any pointers in it * Localizes offsets (converts them to pointers) * Checks for zero offsets in messages where they are not supported Some of this was previously done using custom code in the client, this is now removed.
* Generate demarshallers in clientAlexander Larsson2010-06-182-2/+12
|
* Add python code to automake systemAlexander Larsson2010-06-184-1/+10
|
* Initial import of spice protocol description and demarshall generatorAlexander Larsson2010-06-187-0/+3760
| | | | | | The "spice.proto" file describes in detail the networking prototcol that spice uses and spice_codegen.py can parse this and generate demarshallers for such network messages.
* Use the correctly spelled enum values from the new generated enumsAlexander Larsson2010-06-182-2/+2
|
* Use the new enums for keyboard modifier flagsAlexander Larsson2010-06-182-7/+9
|
* There are multiple line attribute flags enums, use only oneAlexander Larsson2010-06-172-4/+4
|
* Add spice_strnlenAlexander Larsson2010-06-172-0/+14
|
* server: optimize red_pipe_replace_rendered_drawables_with_images (lossy ↵Yonit Halperin2010-06-091-6/+90
| | | | bitmaps support related)
* init/destroy lossy surface regionYonit Halperin2010-06-091-0/+2
|
* enabling jpeg on low bandwidth connectionYonit Halperin2010-06-091-16/+17
|
* not using jpeg when sending a surface to the client (the whole surface)Yonit Halperin2010-06-091-1/+3
| | | | | | When a surface is sent to the client using red_send_surface_image, operations were already performed on it. Thus it may combine, especially if it is a primary surface, both "picture-like" areas and areas that are more "artificial". In order to avoid noticeable artifacts, such surface will be sent lossless.
* send qxl commands to client: support for resending lossy components when ↵Yonit Halperin2010-06-091-16/+639
| | | | jpeg compression is enabled
* infrastructure routines for resending to the client part of surfaces that ↵Yonit Halperin2010-06-091-28/+306
| | | | | | | have been sent lossy. The code also handles cases in which the server doesn't hold anymore these surfaces parts, i.e., when it holds a more updated version of them. This scenario is handled by replacing commands that were rendered, with images.
* introducing lossy and lz compression in red_send_imageYonit Halperin2010-06-091-2/+53
|
* lossy surface regions in the client: infrastructure for tracking and updatingYonit Halperin2010-06-091-0/+160
|
* support for lossy images in the pixmap cache and fill bitsYonit Halperin2010-06-097-39/+241
| | | | | | 1) add an option to determine if a bitmap can be sent lossy to the client 2) when required, replacing lossy cache items with their correspending lossless bitmaps
* JPEG support: introducing jpeg encoding for spice bitmapsYonit Halperin2010-06-0923-45/+956
|
* server: fix bitmap flags assignment in red_send_imageYonit Halperin2010-06-091-2/+2
|
* client: Only invalidate on screen if drawing to the primary surfaceAlexander Larsson2010-06-091-2/+6
|