Browse Library
Sign In Start Free Trial
Close icon Search icon
Account
Browse Library Advanced Search Sign In Start Free Trial

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Learning Python Networking
  • Toc
  • feedback
Learning Python Networking

Learning Python Networking

By : Dr. M. O. Faruque Sarker, Samuel B Washington, Sam Washington
3.7 (7)
close
Learning Python Networking

Learning Python Networking

3.7 (7)
By: Dr. M. O. Faruque Sarker, Samuel B Washington, Sam Washington

Overview of this book

If you're a Python developer or a system administrator with Python experience and you're looking to take your first steps in network programming, then this book is for you. Basic knowledge of Python is assumed.
Table of Contents (12 chapters)
close
close
Preface
Preface
What this book covers
What you need for this book
Who this book is for
Conventions
Reader feedback
Customer support
Free Chapter
1
1. Network Programming and Python
1. Network Programming and Python
An introduction to TCP/IP networks
Network programming with Python
Breaking a few eggs
Summary
2
2. HTTP and Working with the Web
2. HTTP and Working with the Web
Request and response
Requests with urllib
Response objects
Status codes
Handling problems
HTTP headers
Customizing requests
Content negotiation
User agents
Cookies
Redirects
URLs
HTTP methods
Formal inspection
HTTPS
The Requests library
Summary
3
3. APIs in Action
3. APIs in Action
Getting started with XML
The Amazon S3 API
JSON
The Twitter API
HTML and screen scraping
With great power...
Summary
4
4. Engaging with E-mails
4. Engaging with E-mails
E-mail terminologies
Sending e-mails with SMTP
Sending e-mails securely with TLS
Retrieving e-mails by using POP3 with poplib
Retrieving e-mails by using IMAP with imaplib
Sending e-mail attachments
Sending e-mails via the logging module
Summary
5
5. Interacting with Remote Systems
5. Interacting with Remote Systems
Secure shell – access using Python
Transferring files through SFTP
Transferring files with FTP
Fetching Simple Network Management Protocol data
Reading Light-weight Directory Access Protocol data
Sharing files with SAMBA
Summary
6
6. IP and DNS
6. IP and DNS
Retrieving the network configuration of a local machine
Manipulating IP addresses
GeoIP look-ups
NTP clients
Summary
7
7. Programming with Sockets
7. Programming with Sockets
Basics of sockets
Working with TCP sockets
Working with UDP sockets
TCP port forwarding
A non-blocking socket I/O
Securing sockets with TLS/SSL
Creating a custom SSL client/server
Summary
8
8. Client and Server Applications
chevron up
8. Client and Server Applications
Client and server
An echo protocol
A simple echo server
A simple echo client
Concurrent I/O
Multithreading and multiprocessing
A multithreaded echo server
Designing a chat server
A chat protocol
Handling data on persistent connections
A multithreaded chat server
A multithreaded chat client
Event-driven servers
A low-level event-driven chat server
Frameworks
An eventlet-based chat server
An asyncio-based chat server
More on frameworks
Taking our servers forward
Summary
9
9. Applications for the Web
9. Applications for the Web
What's in a web server?
Python and the Web
Flask – a microframework
Hosting Python web applications
Hosting in practice
Summary
10
A. Working with Wireshark
A. Working with Wireshark
Packet sniffers
Wireshark
11
Index
Index

Handling data on persistent connections

A new problem which our persistent connection approach raises is that we can no longer assume that our socket.recv() call will contain data from only one message. In our echo server, because of how we have defined the protocol, we know that as soon as we see a null byte, the message that we have received is complete, and that the sender won't be sending anything further. That is, everything we read in the last socket.recv() call is a part of that message.

In our new setup, we'll be reusing the same connection to send an indefinite number of messages, and these won't be synchronized with the chunks of data that we will pull from each socket.recv(). Hence, it's quite possible that the data from one recv() call will contain data from multiple messages. For example, if we send the following:

caerphilly,
illchester,
brie

Then on the wire they will look like this:

caerphilly\0illchester\0brie\0

Due to the vagaries of network transmission though, a set of successive...

Unlock full access

Continue reading for free

A Packt free trial gives you instant online access to our library of over 7000 practical eBooks and videos, constantly updated with the latest in tech
Start a 7-day FREE trial
End of Section 10
Next Section
bookmark search playlist font-size

Change the font size

margin-width

Change margin width

day-mode

Change background colour

Close icon Search
Country selected
Close icon Your notes and bookmarks

Delete Bookmark

Modal Close icon
Are you sure you want to delete it?
Cancel
Yes, Delete