READMEs: kumina features, clarifications.

This commit is contained in:
Joel Martin 2011-07-14 12:27:04 -05:00
parent 108b617eef
commit 6a7b56d56f
3 changed files with 27 additions and 4 deletions

View File

@ -77,48 +77,70 @@ implementations:
<th>websockify</th>
<th>other/websockify</th>
<th>other/websockify.js</th>
<th>other/kumina</th>
</tr> <tr>
<th>Language</th>
<td>python</td>
<td>C</td>
<td>Node (node.js)</td>
<td>C</td>
</tr> <tr>
<th>Multiproc</th>
<td>yes</td>
<td>yes</td>
<td>yes</td>
<td>no</td>
</tr> <tr>
<th>Daemon</th>
<td>yes</td>
<td>yes</td>
<td>no</td>
<td>no</td>
</tr> <tr>
<th>SSL wss</th>
<td>yes 1</td>
<td>yes</td>
<td>no</td>
<td>no</td>
</tr> <tr>
<th>Flash Policy Server</th>
<td>yes</td>
<td>yes</td>
<td>no</td>
<td>yes</td>
</tr> <tr>
<th>Session Record</th>
<td>yes 2</td>
<td>no</td>
<td>no</td>
<td>no</td>
</tr> <tr>
<th>Web Server</th>
<td>yes</td>
<td>no</td>
<td>no</td>
<td>no</td>
</tr> <tr>
<th>Program Wrap</th>
<td>yes</td>
<td>no</td>
<td>no</td>
<td>no</td>
</tr> <tr>
<th>Hixie 75/76</th>
<th>Multiple targets</th>
<td>no</td>
<td>no</td>
<td>no</td>
<td>yes</td>
</tr> <tr>
<th>Hixie 75</th>
<td>yes</td>
<td>yes</td>
<td>yes</td>
<td>no</td>
</tr> <tr>
<th>Hixie 76</th>
<td>yes</td>
<td>yes</td>
<td>yes</td>
<td>yes</td>
@ -127,6 +149,7 @@ implementations:
<td>yes</td>
<td>no</td>
<td>no</td>
<td>no</td>
</tr>
</table>

View File

@ -21,5 +21,5 @@ kumina: kumina.o
$(CC) $(LDFLAGS) $^ -lresolv -lssl -o $@
clean:
rm -f websockify wswrapper.so *.o
rm -f websockify wswrapper.so kumina *.o

View File

@ -26,8 +26,8 @@ The upstream source of the kumina proxy is [here](https://github.com/kumina/wspr
[This article](http://blog.kumina.nl/2011/06/proxying-and-multiplexing-novnc-using-wsproxy/)
describes the kumina proxy.
kumina is an application that can be run from inetd, which allows noVNC
to connect to an unmodified libvncserver. Furthermore, it makes use of
kumina is an application that is run from inetd, which allows noVNC
to connect to an unmodified VNC server. Furthermore, it makes use of
the recently added support in noVNC for file names. The file name is
used to denote the port number. Say, you connect to: