Python Desktop Server WeblogThis is the Python Desktop Server weblog.RBL == Incompetence- April 30, 2005 Remember my rant about the incompetence of SORBS They got company: rfc-ignorant.org lists .de as a complete domain, because they don't like the whois-interface of the .de toplevel. No, there is no RFC that demands a working whois for domains - especially it's nothing that's in the mail RFCs. But they don't like it and so they just throw it into their silly list. Another RBL you can't use. Actually I am quite sure that all RBL providers are either technically incompetent or totally retarded...http://pyds.muensterland.org/weblog/2005/04/30.html#P256 TooFPy 0.3.6 released- April 26, 2005 This is just the long waiting release of TooFPy - nothing new in the last months, I just hadn't done too much testing with it and so delayed the release until it got a bit more usage. The main changes of this release are: WSGI support (TooFpy can function as a WSGI server) Reactor Chain pattern to add hooks into the code in a non-destructive and non-disruptive manner (already used for server startstop, tuple deleting and for request rewriting) better authentication stuff (IP-based, HTTP-based,.http://pyds.muensterland.org/wiki/toolserver.html The Incompetence of SORBS.NET- April 11, 2005 SORBS.NET runs a RBL service that admins foolish enough can use to block mail from supposedly corrupted or spammy servers. From time to time systems of mine are listed in that list. Usually out of rather stupid reasons: one system was listed because it ran FTP services on some high port numbers and that's defined as being taken over by spammers for the SORBS.NET admins. A recent listing just gives the reason that there are supposedly unknown trojans running on that server - yeah, sure, you...http://pyds.muensterland.org/weblog/2005/04/11.html#P254 ActiveStorage now has a SQLite backend- April 7, 2005 Thanks to Yaroslav Samchu, asfPY now has a SQLite backend. He sent in a first take at this backend and I completed the code so that it now runs with only a few glitches left. One glitch is the support for autoincrementing columns - this isn't done in an atomic way due to the fact that the pysqlite interface (at lest the 1.something series) doesn't support atomic update and fetch on those columns and so I had to do a select max() and a combined insert. The other glitch is support for data types..http://pyds.muensterland.org/weblog/2005/04/07.html#P253 |