|
0
|
1 \documentclass[twocolumn,twoside,9.5pt]{jarticle}
|
|
|
2 \usepackage[dvips]{graphicx}
|
|
|
3 \usepackage{picins}
|
|
|
4 \usepackage{fancyhdr}
|
|
|
5 \pagestyle{fancy}
|
|
3
|
6 \lhead{Technical Reading Writing}
|
|
0
|
7 \rhead{}
|
|
|
8 \cfoot{}
|
|
|
9
|
|
|
10 \setlength{\topmargin}{-1in \addtolength{\topmargin}{15mm}}
|
|
|
11 \setlength{\headheight}{0mm}
|
|
|
12 \setlength{\headsep}{5mm}
|
|
|
13 \setlength{\oddsidemargin}{-1in \addtolength{\oddsidemargin}{11mm}}
|
|
|
14 \setlength{\evensidemargin}{-1in \addtolength{\evensidemargin}{21mm}}
|
|
|
15 \setlength{\textwidth}{181mm}
|
|
|
16 \setlength{\textheight}{261mm}
|
|
|
17 \setlength{\footskip}{0mm}
|
|
|
18 \pagestyle{empty}
|
|
|
19
|
|
|
20 \begin{document}
|
|
3
|
21 \title{System design and implementation for the class using the VNC screen sharing}
|
|
|
22 \author{School register number:085734D Name:Yu Taninari Instructor:Shinji Kono}
|
|
0
|
23 \date{}
|
|
|
24 \maketitle
|
|
|
25 \thispagestyle{fancy}
|
|
|
26
|
|
3
|
27 \section{First}
|
|
|
28 When usually performing teaching,In many cases performed using the projector.
|
|
|
29 but, when performed using the projector It is difficult to be visible at rear side seat.
|
|
|
30 If participation class students have personal computer that it can the teacher's screen display.
|
|
|
31 If it makes students at rear side seat can be seen easily to teachers display.
|
|
|
32 Using VNC can display the teacher's screen to students display.
|
|
|
33 However, the screen will no longer keep up with the progress of the class fell and process it may end up connecting to a PC at the same time teacher of students of multiplayer.
|
|
|
34 This problem happen at same time access to teacher display.
|
|
0
|
35
|
|
3
|
36 In this study, the client into a tree structure so that you can share the screen in multiplayer
|
|
|
37 Do the design and implementation of (TreeVNC) system that is sharing the screen in such a way that will sink the data in order from top to be connected.
|
|
0
|
38
|
|
|
39
|
|
3
|
40 \section{About VNC}
|
|
|
41 VNC(Virtual Network Computing) is Remote Desktop software. It is can be remote operation using 'RFB Protocol'.
|
|
|
42 VNC is divided into the client side and server side, start the server, the client makes a connection to the server.
|
|
0
|
43
|
|
3
|
44 \section{Rfb Protocol}
|
|
0
|
45
|
|
|
46
|
|
3
|
47 \section{Design policy for TreeVNC}
|
|
|
48 First, problem arises when using VNC multiplayer. Since there is many connection,Processing performance falls. it will go down.
|
|
|
49 In order to solve this problem . I developed how the client which received the data of screen drawing pours data to the following client was considered.
|
|
|
50 A client to do screen sharing to becomes VNC server itself.
|
|
|
51 Moreover, I were considered as it is better to connect by a tree structure.
|
|
|
52 PC (Top) which is present in the top of a tree performs management of connection of clients, Only Top node is made to connect with a VNC server. \\
|
|
|
53 This time is created Tree VNC is The above-mentioned method. only screen sharing do(not allow Operation).
|
|
0
|
54
|
|
|
55
|
|
3
|
56 \section{Precedence example}
|
|
|
57 There are Vnc Reflector and VNc Projector in order to reduce the load to a Vnc server.
|
|
0
|
58
|
|
|
59 \subsection{VNC Reflector}
|
|
3
|
60 Vnc Reflector is a program which enters between a Vnc server and a client and performs communication with a Vnc server instead.
|
|
|
61 Because the only client to connect to the Vnc Reflector. we can reduce the load on the Vnc server in order to the connection with a Vnc server serves as only Vnc Reflector.
|
|
0
|
62
|
|
2
|
63 \subsection{Vnc Projector}
|
|
3
|
64 Vnc Projector is screen sharing software using by Broadcast.
|
|
|
65
|
|
|
66 Since Broadcasting is used, there is little load to a server.
|
|
|
67
|
|
|
68 This software is a charge.
|
|
|
69 It is possible to correspond to the wireless LAN, because not use Broadcast.
|
|
2
|
70
|
|
3
|
71 \section{Impliments of TreeVNC}
|
|
|
72 TreeVNC created based on the java version of TightVNCVirewer.TightVNC is free software for VNC.
|
|
|
73 VNC servers created by C++ the Windows version and the Java version is published as of August 9, 2011.
|
|
|
74
|
|
0
|
75
|
|
3
|
76 \subsection{construction of Tree}
|
|
|
77 ients connected to a host as tree structure. The following procedures perform composition of a tree.
|
|
0
|
78 \begin{enumerate}
|
|
3
|
79 \item When a client connects, it connects with the proxy (this proxy will be described to be Top from now on) linked to a host.
|
|
|
80 \item The Top teaches the place which should be connected to a client. (It is taught at this time whether you are parents' number, your and number together)
|
|
|
81 \item A client connects with the node specified from Top.
|
|
0
|
82 \end{enumerate}
|
|
|
83
|
|
|
84
|
|
3
|
85 \subsection{reconstruction of Tree}
|
|
|
86 Since the client is connected in the shape of a tree as for this mounting, if a parent node falls, a child node will also fall together. \\
|
|
|
87 Therefore, reconstruction of a tree is needed. The procedure which reconstructs Tree is followed as follows.
|
|
0
|
88 \begin{enumerate}
|
|
3
|
89 \item A child reports to root that parents be down state.
|
|
|
90 \item when root is reported. orders to become instead of the parents who fell to largest number node.
|
|
|
91 \item The client which received the command from root reconnects with the place where root was specified.
|
|
|
92 \item root updates the list of clients -- new parents' information is taught to the children to whom parents state down.
|
|
|
93 \item The child who doesn't have parents connect to new parents.
|
|
0
|
94 \end{enumerate}
|
|
3
|
95 In this way, Tree can be reconstructed.$\\$
|
|
|
96 When the child to whom the following sauce and parents fell has connected, it is a part of code of the portion which waits for all children's connection.
|
|
0
|
97
|
|
|
98
|
|
3
|
99 \section{Evaluation}
|
|
|
100 TreeVNC was implemented and comparison with Vnc Reflector was performed.
|
|
|
101 Test environment prepares 48 VM(s) on a Blade server, and is TreeVNC and Vnc Reflector besides a Blade server.
|
|
|
102 PC was placed and it experimented by making 48 VM(s) access.
|
|
0
|
103
|
|
3
|
104 \subsection{Compare VncReflector to TreeVNC}
|
|
|
105 As for overconcentrated type Vnc Reflector, the throughput fell from 20 mega to five mega.
|
|
|
106 On the other hand, it has checked that the direction of TreeVNC saved as [ 20 mega ] for a throughput.
|
|
|
107 This is unlike Vnc Reflector 48 units to gain access to a communication band of this is because the client will communicate with each other.
|
|
0
|
108
|
|
3
|
109 \subsection{The advantage and fault of TreeVNC}
|
|
0
|
110
|
|
3
|
111 Since clients exchange data, there is little load to a Vnc server.
|
|
0
|
112
|
|
3
|
113 Since it is not an overconcentrated type, when using by a lot of people, there is little stress of a display.
|
|
0
|
114
|
|
3
|
115 The Top itself can also have a viewer.
|
|
0
|
116
|
|
3
|
117 Communication speed of minutes all up, high load to the switch.
|
|
0
|
118
|
|
|
119
|
|
2
|
120
|
|
3
|
121 \section{Result and Future works}
|
|
|
122 In this research, the screen shared system was developed using VNC and a tree structure.
|
|
|
123 A result a throughput without dropping its connection at 48 sets.
|
|
0
|
124
|
|
3
|
125 Since the test in an actual lesson etc. is omitted, I would like to test whether it can use by actual lesson, although the test on a virtual machine was done this time.
|
|
0
|
126
|
|
3
|
127 Since the portion of UI of a client is not made, I would like to enrich UI and to design an easy-to-use system.
|
|
|
128
|
|
0
|
129
|
|
|
130 \thispagestyle{fancy}
|
|
|
131 \begin{thebibliography}{9}
|
|
|
132
|
|
|
133 \bibitem{VncReflector}{TightVNC: VNC-Compatible Free Remote Control / Remote Desktop Software}:
|
|
|
134 http://vnc-reflector.sourceforge.net/
|
|
|
135 \bibitem{TightVNC}{TightVNC: VNC-Compatible Free Remote Control / Remote Desktop Software}:
|
|
|
136 http://www.tightvnc.com/
|
|
|
137
|
|
|
138 \bibitem{VNC}{Tristan Richardson, Quentin Stafford-fraser, Kenneth R. Wood, Kenneth R. Wood, Andy Hopper}:
|
|
|
139 Virtual Network Computing (1998): Virtual Network Computing (1998)
|
|
|
140
|
|
|
141 \bibitem{ZLIB}{P. Deutsch, J-L. Gailly }:
|
|
|
142 ZLIB Compressed Data Format Specification version 3.3
|
|
|
143
|
|
|
144 \end{thebibliography}
|
|
|
145 \end{document}
|
