Start learning with our library of video tutorials taught by experts. Get started
Viewers: in countries Watching now:
In this course, part of his series of titles on HTML5 and CSS3, author and expert Andy Olsen looks at advanced topics like geolocation, mobile development, web sockets, Web SQL, and web workers. You'll also learn how to communicate between pages downloaded from different servers and how to use the new Ajax features in XMLHttpRequest Level 2. After completing this workshop, developers be well equipped to start utilizing the powerful features of HTML5.
In this lesson we're going to see how to implement a web socket client in an HTML page. It'll talk to a web socket server that I've already written implemented using node js. So if you don't already have node js platform installed in your machine all you need to do is to run this MSI file from the Project files folder. And it'll install node js in your Program files folder on windows. And then to actually start the server running, if you open up a command window, and type this in, so it will run the node js engine, and it'll start socketserverws.js.
That's the name of my web server, that listens on port 8888 for web socket connections. So the web server is now listening on port 8888 for web socket connections and we're going to make those connections from this client here. Now, the way I've written the server is that it'll only accept web socket connections that are issued from a special domain of local hosts. So, for example, if you tried to run the HTML file directly from the file system, the origin that would get sent over to the server would be null.
And the server would reject that connection so I'll illustrate that now. I'll just press enter. So it didn't connect successfully to the web server. The web server rejected the attempt to connect because the origin wasn't local host. If I go back into the command prompt window, you can see that the web server received the attempted connection from the client. It checked the origin of that request against local host. It wasn't local host, it was actually null. That's what happens when you send requests from a file via the file system.
So to run the client correctly, I'm going to close this window and I'm going to run it, through my local host server, like so. So, this will send, as soon as the webpage starts a connection request for the server to say I am local host, can we have a web socket communication. The web server will accept that request and the client and the server can then communicate asynchronously at the same time. So I'll press enter. So the client has now connected to the server, and the server, as we can see here, accepted the request from local host, and the server is sending back every second a message to the client.
Also, the client can send information back to the server so I can type in here prynhawn da. That means good afternoon in Welsh. It's about 5pm here and a beautiful spring afternoon in South Wales so, good afternoon I'll send that to the server. The server receives that message and bounces back a similar response so here's the message the server receivedFOREIGN and it sent back a response to the client which we can see if I scroll down a bit further, there we go. So, thats the message that the client sent the server and this is the response message that the server sent back to the client.
If I close the client, the server realizes the connection's closed, and it outputs a message of that. So, that's how the example works. Let's see how it's implemented from the client's point of view. So in Commodo edit this is the socket client. The good news is that the API in JAVA script for implementing web sockets is actually quite straightforward. The window object has a websocket property. If your browser supports websockets and that object has an API, which allows you to send messages to the server and to receive messages that get sent back from the server. I have a patch here, if you're running this example on the Firefox Mozilla. In Firefox, the property isn't web socket, the property used instead is called mozilla web socket, like so.
Okay? So this part here is just to make sure that the example will work properly if used in Firefox. Obviously, I was using Chrome, so that isn't exactly relevant in this particular example for me. Right, so when the webpage starts up, this is immediate script. This is the URL that I used to connect to the server. The key point here is well a few key points serve as remnant on local host on 8888, that was the port number. The protocol that you use for websocket communication is WS as opposed to HTTP.
So, as soon as you make a request to a ws protocol, the web server knows that it's attempting to use the elevated web socket protocol as opposed to HTTP. So in HTTP, you have HTTP or HTTPS. For web sockets, you use WS or WSS if you want to have secure communication. So that's the URL of the server that I'd like to have a web socket communication with. What you then do is you create a new web socket object using that URL, okay? So that'll attempt to connect to the web server.
Then there are a series of events that you can handle in your client. So, the on open event will occur when you have a connection that's been opened. I have a log method that I'll show you in a moment which just simply displays messages on the web page. And we invoke this method to send data to the server. So as well as handling events, such as on open, and on close, and on method, you can use this function send to send data from the client to the server whenever you want to.
So, we have an Open Gateway here, the client can send the data to the server whenever it wants, and the server can return data to the client whenever it wants. So, this is full duplex, two-way, asynchronous, bidirectional communication offered by WS. If the server sends data back to the client, then it's handled by the onmessage event. So in that case, this will display messages that are incoming but have been sent from the server back to the browser. And then, when the socket connection is closed, this even occurs, okay? So, let me just scroll down a little further.
I'll show you some of these helper functions. So, in the web page we had the opportunity to type in some text like prynhawn da, and to send that data to the server. So when user clicked the Send button on the web page it calls the do send function. And the do send function gets the text that you've typed in and then sends it to the server using the send function that I was talking about a few moments ago.
And if you want to you can send data back to the server by calling the Send function.
There are currently no FAQs about HTML5 Power Workshop.
Access exercise files from a button right under the course name.
Search within course videos and transcripts, and jump right to the results.
Remove icons showing you already watched videos if you want to start over.
Make the video wide, narrow, full-screen, or pop the player out of the page into its own window.
Click on text in the transcript to jump to that spot in the video. As the video plays, the relevant spot in the transcript will be highlighted.