Update to version 0.4.1

*** IMPORTANT NOTE ***

0.4.X is the last minor version to support the Hixie protocol. 0.5.0
will drop the Hixie protocol support. The latest released version of
all major browsers (and web-socket-js) support the IETF 6455 protocol.

- Other changes: add 'include/' sub-dir to source distribution and to
  installed packaged.
This commit is contained in:
Joel Martin 2013-03-12 13:46:45 -05:00
parent d9aedfe7d3
commit db6a7e3e28
4 changed files with 25 additions and 9 deletions

View File

@ -1,6 +1,13 @@
Changes Changes
======= =======
0.4.1 - Mar 12, 2013
--------------------
* ***NOTE*** : 0.5.0 will drop Hixie protocol support
* add include/ directory and remove some dev files from source
distribution.
0.4.0 - Mar 12, 2013 0.4.0 - Mar 12, 2013
-------------------- --------------------

View File

@ -1 +1 @@
include CHANGES.txt *.py README.md LICENSE.txt include CHANGES.txt websockify include README.md LICENSE.txt

View File

@ -10,14 +10,15 @@ the target in both directions.
### WebSockets binary data ### WebSockets binary data
Websockify supports all versions of the WebSockets protocol (Hixie and Websockify 0.4.X supports all versions of the WebSockets protocol
HyBi). The older Hixie versions of the protocol only support UTF-8 (Hixie and HyBi). Starting with websockify 0.5.0, only the HyBi / IETF
text payloads. In order to transport binary data over UTF-8 an 6455 WebSocket protocol is supported.
encoding must used to encapsulate the data within UTF-8.
With Hixie clients, Websockify uses base64 to encode all traffic to The older Hixie versions of the protocol only support UTF-8 text
and from the client. This does not affect the data between websockify payloads. In order to transport binary data over UTF-8 an encoding
and the server. must used to encapsulate the data within UTF-8. With Hixie clients,
Websockify uses base64 to encode all traffic to and from the client.
This does not affect the data between websockify and the server.
With HyBi clients, websockify negotiates whether to base64 encode With HyBi clients, websockify negotiates whether to base64 encode
traffic to and from the client via the subprotocol header traffic to and from the client via the subprotocol header

View File

@ -1,6 +1,6 @@
from setuptools import setup, find_packages from setuptools import setup, find_packages
version = '0.4.0' version = '0.4.1'
name = 'websockify' name = 'websockify'
long_description = open("README.md").read() + "\n" + \ long_description = open("README.md").read() + "\n" + \
open("CHANGES.txt").read() + "\n" open("CHANGES.txt").read() + "\n"
@ -12,6 +12,14 @@ setup(name=name,
classifiers=[ classifiers=[
"Programming Language :: Python", "Programming Language :: Python",
], ],
data_files=[('share/websockify/include',
['include/util.js',
'include/base64.js',
'include/websock.js']),
('share/websockify/include/web-socket-js',
['include/web-socket-js/WebSocketMain.swf',
'include/web-socket-js/swfobject.js',
'include/web-socket-js/web_socket.js'])],
keywords='noVNC websockify', keywords='noVNC websockify',
license='LGPLv3', license='LGPLv3',
url="https://github.com/kanaka/websockify", url="https://github.com/kanaka/websockify",