Log in

No account? Create an account
LiveJournal Development [entries|archive|friends|userinfo]
LiveJournal Development

[ userinfo | livejournal userinfo ]
[ archive | journal archive ]

January 7th, 2003

Customview [Jan. 7th, 2003|12:02 am]
LiveJournal Development


Ok i can't find custom view for the life of me... am i missing something?

the files is customview.cgi

thanks in advanced.
link3 comments|post comment

A New problem [Jan. 7th, 2003|02:39 pm]
LiveJournal Development


Ok for some reason on a lot of the journals i'm getting

HTTP/1.1 200 OK Date: Wed, 08 Jan 2003 22:36:13 GMT Server: Apache-AdvancedExtranetServer/1.3.26 (Mandrake Linux/6.1mdk) mod_perl/1.27 mod_gzip/ mod_ssl/2.8.10 OpenSSL/0.9.6g sxnet/1.2.4 PHP/4.2.3 Cache-Control: private, proxy-revalidate Content-length: 5370 Keep-Alive: timeout=15, max=84 Connection: Keep-Alive, Keep-Alive Content-Type: text/html; charset=utf-8

When you view the journal, it doubles the entry if it only has one, and then prints that between it... this is on my own server and this just started... i'm not sure why it is printing the headers
link4 comments|post comment

Invitation codes [Jan. 7th, 2003|04:21 pm]
LiveJournal Development


What happens to invitation codes when their owner account gets purged?
link20 comments|post comment

(no subject) [Jan. 7th, 2003|08:36 pm]
LiveJournal Development
Hey could somebody tell me where to get perl modules Jcode, Mail::Address and Mail::Words? The installation program lists Mail::Words as a missing module. But the documentation makes no mention of this module. It does list Mail::Base64 as a required module. In any case, I didn't find any exact matches for the three modules at perl.org. Thanks!
link2 comments|post comment

Friends view optimization [Jan. 7th, 2003|09:55 pm]
LiveJournal Development


I just committed a new optimization for the generation of the friends view, where the results from a previous friends page construction can aid a subsequent one, by caching the results from time to time.

Yes, we've done this in the past, but the implementation was always wrong. Changes to the approach this time around:

1) it's not required. if it won't work, it falls back quickly to old algorithm.

2) it doesn't tax the database. very simple schema, and all the real bookkeeping is done in perl (on the cheap webservers), not in the database. there's even a parameter to adjust how often cache updates happen

3) an out-of-date cache (if aforementioned parameter is set to non-zero) still helps the old algorithm. so any cache is good.

The patch is here, for those curious:


I've been testing this for a number of hours this evening, and I'm relatively convinced it works, but the friends view code is some of the trickiest/ugliest in the codebase, so I made it an option for now. If you want to enable it, visit:


Note: the optimization only affects when you're logged in and looking at your own friends view without any filters.

Happy browsing/testing!

Update: newest code live, 3 bugs squished. if your cache is corrupt/old, turn beta testing on again to clear it.... then test out for a few hours before reporting any bugs.
link34 comments|post comment

[ viewing | January 7th, 2003 ]
[ go | Previous Day|Next Day ]