Current File : //opt/rh/rh-python35/root/lib64/python3.5/__pycache__/socketserver.cpython-35.pyc
���\Ja � @ sl d Z d Z d d l Z d d l Z d d l Z d d l Z y d d l Z Wn e k
rl d d l Z Yn Xd d l m
Z d d d d d d
d d d
d d d g Z e e d � r� e j
d d d d g � e e d � r� e j Z n e j Z Gd d � d � Z Gd d � d e � Z Gd d � d e � Z Gd d � d � Z Gd d � d � Z Gd d � d e e � Z Gd d � d e e � Z Gd d
� d
e e � Z Gd d � d e e � Z e e d � r)Gd d � d e � Z Gd! d � d e � Z Gd" d � d e e � Z Gd# d � d e e � Z Gd$ d � d � Z Gd% d
� d
e � Z Gd& d � d e � Z d S)'ap Generic socket server classes.
This module tries to capture the various aspects of defining a server:
For socket-based servers:
- address family:
- AF_INET{,6}: IP (Internet Protocol) sockets (default)
- AF_UNIX: Unix domain sockets
- others, e.g. AF_DECNET are conceivable (see <socket.h>
- socket type:
- SOCK_STREAM (reliable stream, e.g. TCP)
- SOCK_DGRAM (datagrams, e.g. UDP)
For request-based servers (including socket-based):
- client address verification before further looking at the request
(This is actually a hook for any processing that needs to look
at the request before anything else, e.g. logging)
- how to handle multiple requests:
- synchronous (one request is handled at a time)
- forking (each request is handled by a new process)
- threading (each request is handled by a new thread)
The classes in this module favor the server type that is simplest to
write: a synchronous TCP/IP server. This is bad class design, but
save some typing. (There's also the issue that a deep class hierarchy
slows down method lookups.)
There are five classes in an inheritance diagram, four of which represent
synchronous servers of four types:
+------------+
| BaseServer |
+------------+
|
v
+-----------+ +------------------+
| TCPServer |------->| UnixStreamServer |
+-----------+ +------------------+
|
v
+-----------+ +--------------------+
| UDPServer |------->| UnixDatagramServer |
+-----------+ +--------------------+
Note that UnixDatagramServer derives from UDPServer, not from
UnixStreamServer -- the only difference between an IP and a Unix
stream server is the address family, which is simply repeated in both
unix server classes.
Forking and threading versions of each type of server can be created
using the ForkingMixIn and ThreadingMixIn mix-in classes. For
instance, a threading UDP server class is created as follows:
class ThreadingUDPServer(ThreadingMixIn, UDPServer): pass
The Mix-in class must come first, since it overrides a method defined
in UDPServer! Setting the various member variables also changes
the behavior of the underlying server mechanism.
To implement a service, you must derive a class from
BaseRequestHandler and redefine its handle() method. You can then run
various versions of the service by combining one of the server classes
with your request handler class.
The request handler class must be different for datagram or stream
services. This can be hidden by using the request handler
subclasses StreamRequestHandler or DatagramRequestHandler.
Of course, you still have to use your head!
For instance, it makes no sense to use a forking server if the service
contains state in memory that can be modified by requests (since the
modifications in the child process would never reach the initial state
kept in the parent process and passed to each child). In this case,
you can use a threading server, but you will probably have to use
locks to avoid two requests that come in nearly simultaneous to apply
conflicting changes to the server state.
On the other hand, if you are building e.g. an HTTP server, where all
data is stored externally (e.g. in the file system), a synchronous
class will essentially render the service "deaf" while one request is
being handled -- which may be for a very long time if a client is slow
to read all the data it has requested. Here a threading or forking
server is appropriate.
In some cases, it may be appropriate to process part of a request
synchronously, but to finish processing in a forked child depending on
the request data. This can be implemented by using a synchronous
server and doing an explicit fork in the request handler class
handle() method.
Another approach to handling multiple simultaneous requests in an
environment that supports neither threads nor fork (or where these are
too expensive or inappropriate for the service) is to maintain an
explicit table of partially finished requests and to use a selector to
decide which request to work on next (or whether to handle a new
incoming request). This is particularly important for stream services
where each client can potentially be connected for a long time (if
threads or subprocesses cannot be used).
Future work:
- Standard classes for Sun RPC (which uses either UDP or TCP)
- Standard mix-in classes to implement various authentication
and encryption schemes
XXX Open problems:
- What to do with out-of-band data?
BaseServer:
- split generic "request" functionality out into BaseServer class.
Copyright (C) 2000 Luke Kenneth Casson Leighton <lkcl@samba.org>
example: read entries from a SQL database (requires overriding
get_request() to return a table entry from the database).
entry is processed by a RequestHandlerClass.
z0.4� N)� monotonic�
BaseServer� TCPServer� UDPServer�ForkingUDPServer�ForkingTCPServer�ThreadingUDPServer�ThreadingTCPServer�BaseRequestHandler�StreamRequestHandler�DatagramRequestHandler�ThreadingMixIn� ForkingMixIn�AF_UNIX�UnixStreamServer�UnixDatagramServer�ThreadingUnixStreamServer�ThreadingUnixDatagramServer� PollSelectorc @ s� e Z d Z d Z d Z d d � Z d d � Z d d d � Z d
d � Z d d
� Z d d � Z
d d � Z d d � Z d d � Z
d d � Z d d � Z d d � Z d d � Z d d � Z d d! � Z d S)"r a� Base class for server classes.
Methods for the caller:
- __init__(server_address, RequestHandlerClass)
- serve_forever(poll_interval=0.5)
- shutdown()
- handle_request() # if you do not use serve_forever()
- fileno() -> int # for selector
Methods that may be overridden:
- server_bind()
- server_activate()
- get_request() -> request, client_address
- handle_timeout()
- verify_request(request, client_address)
- server_close()
- process_request(request, client_address)
- shutdown_request(request)
- close_request(request)
- service_actions()
- handle_error()
Methods for derived classes:
- finish_request(request, client_address)
Class variables that may be overridden by derived classes or
instances:
- timeout
- address_family
- socket_type
- allow_reuse_address
Instance variables:
- RequestHandlerClass
- socket
Nc C s. | | _ | | _ t j � | _ d | _ d S)z/Constructor. May be extended, do not override.FN)�server_address�RequestHandlerClass� threadingZEvent�_BaseServer__is_shut_down� _BaseServer__shutdown_request)�selfr r � r �</opt/rh/rh-python35/root/usr/lib64/python3.5/socketserver.py�__init__� s zBaseServer.__init__c C s d S)zSCalled by constructor to activate the server.
May be overridden.
Nr )r r r r �server_activate� s zBaseServer.server_activateg �?c C s� | j j � zc t � �S } | j | t j � x6 | j sg | j | � } | rZ | j � | j � q2 WWd QRXWd d | _ | j j
� Xd S)z�Handle one request at a time until shutdown.
Polls for shutdown every poll_interval seconds. Ignores
self.timeout. If you need to do periodic tasks, do them in
another thread.
NF) r �clear�_ServerSelector�register� selectors�
EVENT_READr �select�_handle_request_noblock�service_actions�set)r Z
poll_interval�selector�readyr r r �
serve_forever� s
zBaseServer.serve_foreverc C s d | _ | j j � d S)z�Stops the serve_forever loop.
Blocks until the loop has finished. This must be called while
serve_forever() is running in another thread, or it will
deadlock.
TN)r r �wait)r r r r �shutdown� s zBaseServer.shutdownc C s d S)z�Called by the serve_forever() loop.
May be overridden by a subclass / Mixin to implement any code that
needs to be run during the loop.
Nr )r r r r r& s zBaseServer.service_actionsc
C s� | j j � } | d k r' | j } n! | j d k rH t | | j � } | d k ra t � | } t � �o } | j | t j � xR | j | � } | r� | j
� S| d k r� | t � } | d k r� | j � Sq� WWd QRXd S)zOHandle one request, possibly blocking.
Respects self.timeout.
Nr ) �socketZ
gettimeout�timeout�min�timer r! r" r# r$ r% �handle_timeout)r r. Zdeadliner( r) r r r �handle_request s"
zBaseServer.handle_requestc C s� y | j � \ } } Wn t k
r. d SYn X| j | | � r} y | j | | � Wn% | j | | � | j | � Yn Xd S)z�Handle one request, without blocking.
I assume that selector.select() has returned that the socket is
readable before this function was called, so there should be no risk of
blocking in get_request().
N)� get_request�OSError�verify_request�process_request� handle_error�shutdown_request)r �request�client_addressr r r r% 1 s
z"BaseServer._handle_request_noblockc C s d S)zcCalled if no new request arrives within self.timeout.
Overridden by ForkingMixIn.
Nr )r r r r r1 C s zBaseServer.handle_timeoutc C s d S)znVerify the request. May be overridden.
Return True if we should proceed with this request.
Tr )r r9 r: r r r r5 J s zBaseServer.verify_requestc C s! | j | | � | j | � d S)zVCall finish_request.
Overridden by ForkingMixIn and ThreadingMixIn.
N)�finish_requestr8 )r r9 r: r r r r6 R s zBaseServer.process_requestc C s d S)zDCalled to clean-up the server.
May be overridden.
Nr )r r r r � server_close[ s zBaseServer.server_closec C s | j | | | � d S)z8Finish one request by instantiating RequestHandlerClass.N)r )r r9 r: r r r r; c s zBaseServer.finish_requestc C s | j | � d S)z3Called to shutdown and close an individual request.N)�
close_request)r r9 r r r r8 g s zBaseServer.shutdown_requestc C s d S)z)Called to clean up an individual request.Nr )r r9 r r r r= k s zBaseServer.close_requestc C sP t d d � t d d d �t | � d d l } | j � t d d � d S)ztHandle an error gracefully. May be overridden.
The default is to print a traceback and continue.
�-�( z4Exception happened during processing of request from�end� r N)�print� traceback� print_exc)r r9 r: rC r r r r7 o s
zBaseServer.handle_error)�__name__�
__module__� __qualname__�__doc__r. r r r* r, r& r2 r% r1 r5 r6 r< r; r8 r= r7 r r r r r � s" +
c @ s� e Z d Z d Z e j Z e j Z d Z d Z
d d d � Z d d � Z d d
� Z
d d � Z d
d � Z d d � Z d d � Z d d � Z d S)r a3 Base class for various socket-based server classes.
Defaults to synchronous IP stream (i.e., TCP).
Methods for the caller:
- __init__(server_address, RequestHandlerClass, bind_and_activate=True)
- serve_forever(poll_interval=0.5)
- shutdown()
- handle_request() # if you don't use serve_forever()
- fileno() -> int # for selector
Methods that may be overridden:
- server_bind()
- server_activate()
- get_request() -> request, client_address
- handle_timeout()
- verify_request(request, client_address)
- process_request(request, client_address)
- shutdown_request(request)
- close_request(request)
- handle_error()
Methods for derived classes:
- finish_request(request, client_address)
Class variables that may be overridden by derived classes or
instances:
- timeout
- address_family
- socket_type
- request_queue_size (only for stream sockets)
- allow_reuse_address
Instance variables:
- server_address
- RequestHandlerClass
- socket
� FTc C sh t j | | | � t j | j | j � | _ | rd y | j � | j � Wn | j � � Yn Xd S)z/Constructor. May be extended, do not override.N)r r r- �address_family� socket_type� server_bindr r< )r r r Zbind_and_activater r r r � s
zTCPServer.__init__c C sN | j r% | j j t j t j d � | j j | j � | j j � | _ d S)zOCalled by constructor to bind the socket.
May be overridden.
� N)�allow_reuse_addressr- �
setsockoptZ
SOL_SOCKETZ SO_REUSEADDRZbindr Z getsockname)r r r r rL � s zTCPServer.server_bindc C s | j j | j � d S)zSCalled by constructor to activate the server.
May be overridden.
N)r- Zlisten�request_queue_size)r r r r r � s zTCPServer.server_activatec C s | j j � d S)zDCalled to clean-up the server.
May be overridden.
N)r- �close)r r r r r< � s zTCPServer.server_closec C s
| j j � S)zMReturn socket file number.
Interface required by selector.
)r- �fileno)r r r r rR � s zTCPServer.filenoc C s
| j j � S)zYGet the request and client address from the socket.
May be overridden.
)r- Zaccept)r r r r r3 � s zTCPServer.get_requestc C s: y | j t j � Wn t k
r( Yn X| j | � d S)z3Called to shutdown and close an individual request.N)r, r- ZSHUT_WRr4 r= )r r9 r r r r8 � s
zTCPServer.shutdown_requestc C s | j � d S)z)Called to clean up an individual request.N)rQ )r r9 r r r r= � s zTCPServer.close_requestN)rE rF rG rH r- ZAF_INETrJ Z SOCK_STREAMrK rP rN r rL r r< rR r3 r8 r= r r r r r } s -
c @ s[ e Z d Z d Z d Z e j Z d Z d d � Z d d � Z
d d � Z d
d � Z d S)
r zUDP server class.Fi c C s. | j j | j � \ } } | | j f | f S)N)r- Zrecvfrom�max_packet_size)r �dataZ client_addrr r r r3 s zUDPServer.get_requestc C s d S)Nr )r r r r r s zUDPServer.server_activatec C s | j | � d S)N)r= )r r9 r r r r8
s zUDPServer.shutdown_requestc C s d S)Nr )r r9 r r r r= s zUDPServer.close_requestN)
rE rF rG rH rN r- Z
SOCK_DGRAMrK rS r3 r r8 r= r r r r r � s c @ sX e Z d Z d Z d Z d Z d Z d d � Z d d � Z d d
� Z d d � Z
d S)
r z5Mix-in class to handle each request in a new process.i, Nr? c C s | j d k r d Sx| t | j � | j k r� y, t j d d � \ } } | j j | � Wq t k
r{ | j j � Yq t k
r� PYq Xq Wx| | j j � D]k } y/ t j | t j
� \ } } | j j | � Wq� t k
r� | j j | � Yq� t k
r Yq� Xq� Wd S)z7Internal routine to wait for children that have exited.NrM r ���) �active_children�len� max_children�os�waitpid�discard�ChildProcessErrorr r4 �copy�WNOHANG)r �pid�_r r r �collect_children s$
z ForkingMixIn.collect_childrenc C s | j � d S)znWait for zombies after self.timeout seconds of inactivity.
May be extended, do not override.
N)ra )r r r r r1 ? s zForkingMixIn.handle_timeoutc C s | j � d S)z�Collect the zombie child processes regularly in the ForkingMixIn.
service_actions is called in the BaseServer's serve_forver loop.
N)ra )r r r r r& F s z ForkingMixIn.service_actionsc C s� t j � } | rN | j d k r- t � | _ | j j | � | j | � d Sy. | j | | � | j | � t j d � Wn: z! | j | | � | j | � Wd t j d � XYn Xd S)z-Fork a new subprocess to process the request.Nr rM )
rY �forkrV r' �addr= r; r8 �_exitr7 )r r9 r: r_ r r r r6 M s
z ForkingMixIn.process_request) rE rF rG rH r. rV rX ra r1 r& r6 r r r r r s " c @ s4 e Z d Z d Z d Z d d � Z d d � Z d S)r
z4Mix-in class to handle each request in a new thread.Fc C sM y! | j | | � | j | � Wn% | j | | � | j | � Yn Xd S)zgSame as in BaseServer but as a thread.
In addition, exception handling is done here.
N)r; r8 r7 )r r9 r: r r r �process_request_threadm s z%ThreadingMixIn.process_request_threadc C s; t j d | j d | | f � } | j | _ | j � d S)z*Start a new thread to process the request.�target�argsN)r ZThreadre �daemon_threadsZdaemon�start)r r9 r: �tr r r r6 z s z ThreadingMixIn.process_requestN)rE rF rG rH rh re r6 r r r r r
f s
c @ s e Z d Z d S)r N)rE rF rG r r r r r � s c @ s e Z d Z d S)r N)rE rF rG r r r r r � s c @ s e Z d Z d S)r N)rE rF rG r r r r r � s c @ s e Z d Z d S)r N)rE rF rG r r r r r � s c @ s e Z d Z e j Z d S)r N)rE rF rG r- r rJ r r r r r � s c @ s e Z d Z e j Z d S)r N)rE rF rG r- r rJ r r r r r � s c @ s e Z d Z d S)r N)rE rF rG r r r r r � s c @ s e Z d Z d S)r N)rE rF rG r r r r r � s c @ sF e Z d Z d Z d d � Z d d � Z d d � Z d d � Z d
S) r
a� Base class for request handler classes.
This class is instantiated for each request to be handled. The
constructor sets the instance variables request, client_address
and server, and then calls the handle() method. To implement a
specific service, all you need to do is to derive a class which
defines a handle() method.
The handle() method can find the request as self.request, the
client address as self.client_address, and the server (in case it
needs access to per-server information) as self.server. Since a
separate instance is created for each request, the handle() method
can define arbitrary other instance variariables.
c
C sE | | _ | | _ | | _ | j � z | j � Wd | j � Xd S)N)r9 r: �server�setup�handle�finish)r r9 r: rk r r r r � s
zBaseRequestHandler.__init__c C s d S)Nr )r r r r rl � s zBaseRequestHandler.setupc C s d S)Nr )r r r r rm � s zBaseRequestHandler.handlec C s d S)Nr )r r r r rn � s zBaseRequestHandler.finishN)rE rF rG rH r rl rm rn r r r r r
� s
c @ sF e Z d Z d Z d
Z d Z d Z d Z d d � Z d d � Z d S) r z4Define self.rfile and self.wfile for stream sockets.rM r NFc C s� | j | _ | j d k r. | j j | j � | j rS | j j t j t j d � | j j d | j
� | _ | j j d | j � | _
d S)NT�rb�wb)r9 Z
connectionr. Z
settimeout�disable_nagle_algorithmrO r- Z IPPROTO_TCPZ TCP_NODELAY�makefile�rbufsize�rfile�wbufsize�wfile)r r r r rl � s
zStreamRequestHandler.setupc C sS | j j s5 y | j j � Wn t j k
r4 Yn X| j j � | j j � d S)N)rv �closed�flushr- �errorrQ rt )r r r r rn � s
zStreamRequestHandler.finishrU )
rE rF rG rH rs ru r. rq rl rn r r r r r � s
c @ s. e Z d Z d Z d d � Z d d � Z d S)r z6Define self.rfile and self.wfile for datagram sockets.c C sG d d l m } | j \ | _ | _ | | j � | _ | � | _ d S)Nr )�BytesIO)�iorz r9 Zpacketr- rt rv )r rz r r r rl � s z DatagramRequestHandler.setupc C s# | j j | j j � | j � d S)N)r- Zsendtorv �getvaluer: )r r r r rn � s z DatagramRequestHandler.finishN)rE rF rG rH rl rn r r r r r � s )!rH � __version__r- r" rY �errnor � ImportErrorZdummy_threadingr0 r �__all__�hasattr�extendr r ZSelectSelectorr r r r r
r r r r r r r r r
r r r r r r �<module>w sL
�~Q .+
Rosenblum TV: Video training, virtual workshops, classes, tutorials
RE-INVENTING THE TELEVISION NEWS BUSINESS*
A revolution in video storytelling
Creating entirely new & cost-effective production methods
From the world leaders in video production training and the creators of Character Driven Storytelling™
*and every other business that uses video
WHAT WE DO
Over the past 35 years, we have designed, built or restructured some of the most powerful news and journalism companies in the world.
We replace the traditional TV news ‘crew’ with one highly trained journalist, working alone with nothing but an iPhone.
No more TV news ‘crews’, no editors and no field producers.
This is television news done the way newspaper journalism is done – one reporter with their electronic pad and pencil.
In doing this, we can cut the cost of production by as much as 75% while increasing ratings and audience engagement.
In the place of conventional TV news ‘packages’ – ie, reporter stand up, interview, b-roll, man on the street, we marry great journalism with Netflix and Hollywood storytelling.
It’s a combination that works.
We have taken most of our clients to #1 in their respective markets.
And it’s not just for news. Any company, any profit, any NGO and anyone else who is online needs to tell their story in compelling yet cost-effective video. We can teach you to do that. Either in person or virtually.
EXAMPLES OF WHAT WE CAN TEACH YOUR STAFF TO PRODUCE
ITAY HOD
Itay Hod, MMJ with KPIX/CBS in San Francisco, took the 5-Day Intensive Video Storytelling Bootcamp in 2018.
Because he works alone, with only an iPhone, he was able to embed himself with a homeless family.
Here’s the story he produced in a one-day turn.
KIET DO
Kiet Do, an MMJ with KPIX/CBS in San Francisco, took the 5-Day Intensive Video Storytelling Bootcamp in 2021.
Here is a story he produced, all on his own, with only an iPhone and in a one-day turn.
TAYLOR SCHAUB
Taylor Schaub, an MMJ with Spectrum News 1 in LA, took the 5-Day Intensive Video Storytelling Bootcamp in 2023.
Here is a story he turned in only one day, using only an iPhone. It was the first video story he ever did and it was nominated for an Emmy.
THE BOOTCAMP
How do we convert stations and whole networks to working in this way?
Since 1988, we have run intensive 5-Day Video Storytelling Bootcamps
We have done these all over the world.
These are hands-on bootcamps, and participants learn an entirely new way of creating TV news stories.
-We shoot at a 3:1 ratio or lower, so turnaround times are fast.
-We go directly from camera to timelilne and edit – no written scripts. We work in the medium of pictures and sound.
-We are entirely character-driven.
-We are driven by pictures and real events.
-We are focused almost entirely on ’the viewer experience’.
Since 1988, more than 70,000 journalists around the world have taken our bootcamps, either in person on virtualy.
We have started to work with CBS News, bringing our ideas of character-driven storytelling to one of the most successful and biggest networks in the United States. Since beginning to work with them ratings have climbed and more importantly, audience engagement is through the ceiling.
We started New York Times Television in 1990 and it was the first paper to be brought into the world of TV. It quickly became one of the most successful non-fiction production companies in the United States. The series and documentaries we produced won many awards including multiple Emmys.
We have been working with the BBC since the year 2000 helping to convert their national news network to our visual storytelling technique. Most recently we have trained teams from their sports, documentaries, and comedy divisions to make character-driven stories using only smartphones.
For the past five years we have worked with Spectrum News to introduce and train their journalists on visual, character driven storytelling using smartphones helping to create a different kind of local news for their network of 24-Hour News Stations across the United States.
In 2006, we were approached by the United Nations. Rather than rely on news outlets, it would be much easier to train the field operatives to produce their own stories. We spent two years working with the UN, training more than 100 of their staff in bootcamps in Geneva and Nairobi.
We trained 50 print reporters at the paper to shoot and tell their own stories, in conjunction with their print work. We built a TV newsroom in their existing print newsroom – you could not ask for a better set and they began to live stream their stories in conjunction with their print work.
We spent two years with McGraw Hill, training more than 150 of their staffers, making them completely video literate. McGraw/Hill media properties we transit included Business Week, Aviation Week, (what was the name of the architecture magazine), and JD Power and Associates.
In 1990, we were approached by The Voice of America, the official broadcasting agency for the United States Government. When we met with VOA, they were only a short wave radio broadcaster, but working with them, we took them into television, launching VOA-TV.
British based Oyster Yachts makes some of the finest yachts in the world. Like every other company, they had to find a way to feed the never-ending video demands of social media – sites like Instagram and TikTok. We trained the Oyster staff to tell their own stories, using only iPhones.
We were approached by SEPA, the Scottish Environmental Protection Agency because they had to continually find a way to ‘feed the media beast’. The result was that SEPA was able to tell their own stories, whenever they wanted, and at almost no additional cost.
Michael Rosenblum has been writing about the media since 1988. His work and ideas have appeared in The Guardian, The Huffington Post, Ilkeston Life and many other publications.
He has been blogging regularly for the past 35 years on this subject. Having taught media studies at Columbia University, NYU and now the University of Oxford, he is considered an expert on this subject.
Continue reading this post or look back at previous posts.
