Introduce zip compression

yrift / jwebsocket

Automatically exported from code.google.com/p/jwebsocket

0 stars 0 forks source link

Introduce zip compression #39

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago

Especially when exchanging huge data packets between the server and clients 
that support zip compression it makes sense to think about introducing such 
compression (eg. for file transfer). Of course it will be hard to implement zip 
support for browsers in Javascript but for java client it will be a welcome 
improvement.
The server therefore need to "know" if a certain client has zip/unzip 
capabilities.
Here we should think of some general approach how the server can request 
clients capabilities! See separate issue.

Original issue reported on code.google.com by fivefeetfurther@gmail.com on 12 Aug 2010 at 12:12

GoogleCodeExporter commented 8 years ago

Original comment by fivefeetfurther@gmail.com on 12 Aug 2010 at 12:15

Added labels: Type-Enhancement
Removed labels: Type-Defect

GoogleCodeExporter commented 8 years ago

Original comment by fivefeetfurther@gmail.com on 12 Aug 2010 at 12:16

Changed title: Introduce zip compression

GoogleCodeExporter commented 8 years ago

why not use a standard deflate/gzip algorithm? 

deflate basically resembles gzip without the checksum, which saves some more 
bytes. This will increase efficiency when compressing smaller messages

Original comment by gimpelmo...@gmail.com on 8 Sep 2010 at 11:46

GoogleCodeExporter commented 8 years ago

Can you provide or recommend some code (links) that inflates/deflates data in 
JavaScript and in Java as well, so that we can use it on both sides?

Original comment by fivefeetfurther@gmail.com on 9 Sep 2010 at 1:35

GoogleCodeExporter commented 8 years ago

Original comment by fivefeetfurther@gmail.com on 14 Oct 2010 at 2:29

Added labels: Milestone-v1.2

GoogleCodeExporter commented 8 years ago

Compression is planned to be a known extension as part of the specification.
See 
http://tools.ietf.org/html/draft-ietf-hybi-thewebsocketprotocol-03#section-8.1
So you don't need to implement it for the JavaScript client. In Java you could 
use java.util.zip.

Original comment by roderick...@gmail.com on 23 Oct 2010 at 7:46

GoogleCodeExporter commented 8 years ago

hi, is anyone know if compression is availlable finally? i understand that 
websockets will include it nativelly but in the mean time if i want to use 
FlashBridge and i want to transfert data to 10 000 clients i really need to 
compresse, else it will be 10k f data at each second ... or maybe i dont 
understand somthing :) any help at this point if very welcome... thank you

Original comment by charette...@gmail.com on 5 Nov 2010 at 6:34

GoogleCodeExporter commented 8 years ago

Hi charrettedavid,

unfortunately the specification phase of the websocket protocol is still not 
finished and will probably be subject to further changes. I currently don't 
know any browser that already supports the compression, chrome is the first one 
who at least supports SSL (wss://). I'm sorry I have to answer that it still 
will take a while, however on the jWebSocket server side it will be provided in 
December. You will be able to use it in all Java SE, Android and Java ME 
clients (Symbian and BlackBerry) but on the browser side we'll have to wait 
until they implement it :-(

Best Regards
Alex

Original comment by fivefeetfurther@gmail.com on 5 Nov 2010 at 6:39