Google wave, django and urlize

Django’s urlize filter and google wave urls do no play well together.

Django replaces the ‘!’ in the url with a %21 – but google cannot handle these urls. I suspect the fault lies on Wave’s site

Reverse proxying with pound

Reverse proxying is a technique where a we- server receives requests and then forwards them to other web-servers. If one is interested in performance it can be used for load balancing.

For more run-of-the-mill usage it can be used to combine together web services which work in disparate ways together. E.g. you might be using a python rpc services, django, perl, as well as an http server.

Reverse proxying is supported by apache, also many of the tasks that might otherwise be achieved by reverse proxying can be done in apache in process (e.g modpython, modphp etc) producing higher performace, but with an overhead in reading configuration files, head-scratching, looking for any form of logging and cursing violently.

Pounds is a light weight reverse proxy, which functions only as a web proxy. It seems to be *very* simple to configure – it probably just took me less than 5 minutes to get it working – whilst I suspect getting this working in apache would have taken considerably longer.

Making gnu screen work

This post describes how to get gnu screen working quite well.

http://www.lowlevelmanager.com/2009/09/pair-programming-with-gnu-screen.htmlhttp://www.lowlevelmanager.com/2009/09/pair-programming-with-gnu-screen.html

Random gnu screen tips:

“C-a F” can be used to make gnu see the full window size (useful if you want a vim or emacs with shared windows).