zepheira / akara Goto Github PK

https://github.com/zepheira/akara/blob/master/lib/services.py
Lines 306 and 392 are repeated: _no_slashes(path)

We used to have notifications to the Akara group from github, but inMarch, 2011 the service made a change to the notification e-mail headers which stymies this. Unfortunately, as you can see in the comments from others with this problem, github staff argue "You should only be sending your notifications to your own email address," which is frankly silly. It seems we'll have to implement some sort of intermediary that can forward notification messages to the group.

It would be useful for Akara to properly rotate all of its logs in response to a signal. There is some start to this with the rotate command line instruction, but the implementation is incomplete, skipping the access log and neglecting to close the original fd and open a new one. There is also no need to go down the path of reinventing handling rotation from within Akara, this can reliably be given to the operating system to deal with.

There may be some issue with multiprocess safety with the current logging implementation. The Python documentation on the subject suggests using a socket listener for all processes to send log messages to. Presumably allowing the log listener to handle log closing / opening would be sufficient.

Servers such as Squid and Apache implement delay pools as a mechanism to prevent problematic or abusive request patterns. See also:

• http://www.deckle.co.za/squid-users-guide/Access_Control_and_Access_Control_Operators#Delay_Classes
• http://stackoverflow.com/questions/131681/apache-rate-limiting-options
• http://wiki.squid-cache.org/Features/DelayPools

For now Akara deployments can just lurk behind reverse proxies with such features turned on, but it might be useful to have some primitive facilities for this.