Interfacing between the Web UI and the root server

After much research into different methods of updating the UI as if it were live, we came up with three different methods of communication. The first method we found was WebSockets, which allows you to send data over a single socket. This would allow us to send all the data we needed to the user’s web browser without much trouble. The only problem is that WebSockets is not fully compatible with every web browser. Firefox 4 and Opera 11 have disabled this feature in fear of an exploit. Chrome 4 and Safari 5 continue to use the feature but appear to be planing to disable the feature if actual exploit code is developed. Until this protocol is revised it does not seem like a smart idea to write our program relying on a feature that will most likely not be enabled. From there the next idea was to build a plug in for all the major web browsers which would basically create a socket and pretended the web browser had WebSockets. The problem with this approach is that we would need to design plug ins for each web browser. While building web browser plug ins is an acceptable option, the simplistic option is to use rapid AJAX requests. This idea came from the APE (Ajax Push Engine), however instead of using APE we will be incorporating the feature into our program, allowing the user an easier time configuring their program.

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: