Name: Pythonによるソケットチュートリアル 3 パート1 - データの送受信 (Sockets Tutorial with Python 3 part 1 - sending and receiving data)
Uploaded: 2021-01-14T10:36:20.000Z
Duration: 14 min 27 s
Description: VoiceTubeの動画で発音を聞きながら英語表現を覚えよう！学べる英語：

And welcome to a sockets with python tutorial.

So we got a lot of stuff to cover, so let's get into it.

So I've got a serve it up high in a client dot pine already created.

So if you haven't done that, which probably haven't go ahead and make two files and we're gonna get started in the server ID up high.

So to get started, we're going to import socket Now.

Socket is part of your standard library, so you won't need to install that or anything like that.

Now we want to do is define our socket objects.

So s equals socket dot socket and the socket family type is a f i net.

And then the actual type of socket is going to be socket dot sock stream.

Now, if I net corresponds to I p V four and socks stream corresponds to TCP, So this will be a streaming socket.

And if anybody knows what a f net like, why Why is it called?

If I know like, why don't we just say socket dot I don't know.

Now what we want to do is bind that socket.

So s dot bind, and we want to bind it to a to pull based on.

But anyway, the Tupelo will be in this case because of the type of socket, and I pee in a port.

So we're actually just gonna host the server on the same machine that we have the code.

So we're gonna bind to socket dot Get host name.

So whatever the host name is, basically local host and then the port.

We're gonna go with 1234 You can go with any pre match four digit port.

Lower digits are generally gonna be already occupied by some other program, and you just don't want to step on their toes and more likely they're going to step on your toes.

So once we've bound that socket also, let's just talk real briefly.

Um, generally gonna like two end points, right to have a communication.

So that's just the endpoint that receives data.

So with a socket, you send and you receive data.

So the socket itself is not the communication.

It's just the end point that, like, receives that communication on that end point sits at an I p in a port, so we will stop bind that socket.

Now what we wanna do is s dot Lissy, this is our server.

We're gonna be making some connections to the server.

So this server has to be prepared for these incoming connections, and this server will prepare and leave a queue of five.

So if it's under some sort of heavy load and like multiple connections air coming in so fast that it can't respond quickly enough and they started stacking up, we'll have a queue of five.

Should be more than enough for our purposes.

So then we were going to say is now we're just gonna listen basically forever for connections.

And if we get one witness, a client socket and then address equals s dot except so anybody connects.

Hey, we're happy to see you were gonna connect.

Uh, and then we're going to store the client socket object into this variable client socket.

And then address is where are they coming from?

We can accept this and then the clients socket.

This is just another socket object much like this.

This socket will receive information as we will eventually describe in client dot pie.

So once we've got that connection, let's just print some general debugging f strings.

Ah, address has been stab established exclamation mark because this is serious business.

Okay, so now we're gonna do is client socket dot send.

So we're actually going to send information to the client socket, which I feel like is weird, Like the client socket is a socket object, but it's like a foreign socket objects, so we're going to send information to it, But I almost feel like I don't know, it would make more sense to me if, like, we did s dot send and then we passed in client socket.

This feels weird to me, but Anyways, this is like our local version of the client socket.

So to send information to that client, we're gonna say client socket dot send What do we want to send to this person?

You also could just do like a string and then dot and code or whatever.

Anyway, is there to say, here, welcome to the server.

So now that's pretty much all we need to do to send some information, so I'll save that.

Now, this is not nearly enough for regular use, But this a basic examples base because I could make it.

So now we're gonna work on our client dot pies.

So I'm actually gonna copy paste that information now, this socket rather than binding instead, what this socket really wants to do is connect, So we're gonna say s dot connect and then we pass a to pull again of the I p in the port that we wish to connect to in this case.

It's socket dot Get host name and the I P same is 41234 Now often is the case.

Your client will be like remote to your server.

It won't actually be on the same machine.

So with sockets you can communicate to and from python programs on the same machine on, like a locally networked set of machines or even remotely networked machines.

In most cases, you're probably not actually going to use socket dot get host name or at least not all of the cases.

You'll connect to an actual public I pee or something like that or a look alike.

But for now, we're gonna do everything on the same machine so everybody can follow along.

So we make our connection and, um, we could be done, but we're gonna accept that message that was sent to us.

So we're to say message equals s dot ar e c v for receive and we're gonna receive.

So you've got a stream you have to decide in how big of chump chunk chunks.

Er, how big chunks of data do we want to receive at a time?

But it really depends on what you're doing.

Like if you're sending massive files, you wouldn't want a really tiny buffer size.

You might want something a little larger.

字幕リスト動画再生

Pythonによるソケットチュートリアル 3 パート1 - データの送受信 (Sockets Tutorial with Python 3 part 1 - sending and receiving data)

stuff

weird

eventually

decent