User Tools

Site Tools


programming:python:py-prefork-server

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revisionBoth sides next revision
programming:python:py-prefork-server [2015/01/03 05:53] – [Hooks] jayprogramming:python:py-prefork-server [2015/01/03 05:54] – [Hooks] jay
Line 87: Line 87:
 == initialize(self) == == initialize(self) ==
 Rather than reimplementing __init__, which you can do instead, you can just override this and setup variables and such that you need to set up.  This is the recommended approach.  Note that this is only called once, when the class is initialized.  This is **NOT** called on each new connection.  Use ''post_accept()'' for that purpose. Rather than reimplementing __init__, which you can do instead, you can just override this and setup variables and such that you need to set up.  This is the recommended approach.  Note that this is only called once, when the class is initialized.  This is **NOT** called on each new connection.  Use ''post_accept()'' for that purpose.
 +
 +== pre_bind(self) ==
 +This hook is called before the main socket is created and bound to the ip:port.  This is similar to the ''initialize()'' hook in the child class.  You can use this to set up global variables, etc.  Note that this will **only** be called if you are using reuse_port as the socket will be bound in the child process.
 +
 +== post_bind(self) ==
 +As you might have guessed, this is called right after the ''accept()'' socket has been created and bound.  Note that this will **only** be called if you are using reuse_port as the socket will be bound in the child process.
  
 == post_accept(self) == == post_accept(self) ==
programming/python/py-prefork-server.txt · Last modified: 2023/11/10 20:06 by jay