Hula Girl and the X-Pods
I spent some time this week learning python. PyGTK specifically. I've been writing a little config app for abe. Along the way, I found a nifty
little bug in gtk_file_chooser_set_filename () as shipped in GTK+ 2.6.1. Calling it on an existant file, then running the
GtkFileChooserDialog will run the chooser and display the folder where the file lives, but not select the file. It does however work, if you call it
after the dialog is open, say in a map callback handler (thanks Ray for that suggestion).
I'm also now browser team lead for whatever that's worth. Welcome Hula Girl, and the X-Pods, too. Such a great band name....
Lockdown in sector 4!
Our system indicates unusual usage of your account. In order to protect Gmail users from potentially harmful use of Gmail, this account has been disabled for up to 24 hours.
If you are using any third party software that interacts with your Gmail account, please disable it or adjust it so that its use complies with the Gmail Terms of Use. If you feel that you have been using your Gmail account according to the Terms of Use or otherwise normally, please contact us at gmail-lockdown google com to report this problem.
Hmm, that makes Gmail somewhat less viable for my bugmail habits.... Mail sent. Sigh.
Surfing the pipeline
Apparently, there was an article posted recently that suggests users enable HTTP/1.1 pipelining to boost their performance while using the web. Since then, I have gotten only about 50 bajillion requests to enable it by default in my Fedora RPMs. Sorry guys. There are issues with some web servers and proxies that I just can't ignore. I talked to darin about it and here's an excerpt from our discussion:
<caillon> darin, i remember there being some proxy/web servers that don't like pipelining which is why we disable it by default... is that still a problem? and if so, do you know which ones?
<darin> caillon: yes, that is still a problem. are you talking about that recent article about improving firefox perforamnce by enabling pipelining?
<caillon> yes
<darin> caillon: the problem is that some broken virtual host servers and other transparent HTTP gateways sit in front of Apache 2.x and other good servers... and unfortunately they do not always inject a Via head 93230 er that would allow us to implement a blacklisting scheme.
<darin> caillon: it probably breaks a lot of major sites.. would not want to do e-commerce with pipelining enabled
<darin> caillon: i know that the AOL screenname signon service used to fail when pipelining was enabled
<darin> caillon: just search bugzilla for status whiteboard = [pipelining]
<caillon> darin, yeah. that's more or less what I thought.
<darin> caillon: i heard that opera 8 will have pipelining enabled, so... i may try to implement whatever fallback strategy they are using.
<mcsmurf> bild.de is a big site which breaks with pipelining enabled (at least until you reload a few times)
<darin> Apache 1.3 CGI cannot handle pipelined requests
<mcsmurf> Apache/1.3.27 Server at www.bild.t-online.de Port 80
<darin> yeah, we could blacklist Apache... but it would alsobe pretty easy to create failover code for it since it fails in the simple case (i.e., it just ignores pipelined requests)
<darin> a timeout is all we need
<darin> other servers send back garbage when they get a pipelined request :(
Bottom line is, while it may help some users, it will negatively impact a fair chunk of users. Feel free to enable it yourself, but use it at your own risk.
