The music rocks, but like. I don't like blogs that make me register to leave a comment. Luckily vox stopped doing this (or I'd be now throwing stones, sitting in a glasshouse). Which is totally unrelated to the fact that Justice rocks. I bought an album last week through Amazon, and it totally rocks. I can't find the CD now, but I'll let you know what it's called next time.
[via]
It looks like Ubuntu will become the NetBSD of all Linux. Like they say, that NetBSD runs on just about any plattform, lately Ubuntu seems to follow in those footsteps. Of course I haven't checked too thorough if NetBSD really runs on a PS3, but then again, there are rumours that a port is in the works and then I don't care that much - yet.
Anyway, Ubuntu on a PS3:
http://news.softpedia.com/news/Ubuntu-7-10-on-PS3-73272.shtml
I didn't know yet, but this makes me want a PS3 even more. :-)
[via]
There are more pictures from that Saturday here.
After I posted my File_S3 proposal on Wednesday all hell broke loose yesterday. In the process it turned out that the code I originally used to build this class is obviously by Caesar D. Rodas (who also commented on my blog entry) and got pretty upset - I can understand.
Follow the discussion:
- http://www.nabble.com/-PEPr--Proposal-for-File-System%3A%3AS3-tf4949599.html
- http://www.nabble.com/-PEPr--Comment-on-File-System%3A%3AS3-tf4953679.html
Last night I managed to get in touch with my project manager at that time, at that company and he strongly believed they (the company) owned all IP on the code and he was even more surprised when I told him about the mess it had gotten myself in. Of course this also blows for them, since they obviously got ripped off in the process.
As always - there is a lot to learn from open source, the number one lesson is, "If you don't have a clean track record of code, don't use it!". Though this is sometimes not as black and white as one would like.
Two thoughts of the moment:
- a search engine for code and fuzzy checksums
- I see why certain companies like CLAs
- ... and a third: I need coffee!
UPDATE, 2007/12/07 8:00 AM: Make sure to check the comments, James and Adam offer valuable advice!
For a couple weeks now we kept on saying that we need a checklist of what we need on a server in order to make the site run - now since we setup the neato bonito cluster last week the checklist all of the sudden had a higher priority and I took an hour or so to create that last night.
In the process I used a nifty code snippet by Adam Harvey, to do my PEAR package checking and basically added a loop through get_loaded_extensions() and a shell_exec('cd /foo && svn info') to make it complete. Now season the script with with some CSS, and you have your very own phpChecklist and got yourself some piece of mind.
All this code snippeting and code snippet formatting in VOX is not as trivial as I would like - so anyway, I am sure you get an impression of what I mean.
Just added my File_S3 proposal to PEPR.
Check it out, give it a wirllllll - gimme feedback:
http://pear.php.net/pepr/pepr-proposal-show.php?id=519
So basically what this package allows you to do is, you can open/write/delete files and directories (aka buckets) directly into Amazon S3 referencing it by paths like s3://my_fancy_bucket/file.
And thanks to Darshan from easybib who pretty much sponsors my time on anything pear-related right now.
This morning I rolled another release of HTTP_Session2 and uploaded it to PEAR. So what can you use HTTP_Session2 for and what's new in this release?
The usage question was pretty simple for me, at my current one and only gig we run four web servers behind a loadbalancer and since I'm not a fan of NFS shared storage and writing to it I decided that we could utilize our database powerhouses to store our session data. The other option is what commonly in the cluster-loadbalancing-context is referred to as stickyness, which means that a user is kept on one server during the session, but this adds more load on the loadbalancer itself and it defeats the scalability and hot-failover thing for me.
So this is where HTTP_Session2 comes in and saves the day - I must add, that it's a pretty easy drop-in replacement for regular session calls and works like a charm.
HTTP_Session2 currently supports PostgreSQL and MySQL(i). Except for the garbage collection, which is (oddly) very database specific, others backends should work as well, but we had no time to test that yet.
What's new in 0.6.0?
- We decided to remove the MDB and Creole containers
We felt no one was using either one since MDB is very old and almost everyone is using either DB or its successor MDB2. And for Creole - no idea. I toyed with it briefly at my last job but didn't really fall i love with it. So if you are a Creole user and happen to be using HTTP_Session2, I'll revert and you can maintain it. ;-) - Added the new MDB2 container
- Fixed smaller bugs and lots of CS
- Change stability to beta.
- Develop a PDO or Doctrine container to move to PHP5 completely.
- A File container/driver to for example store sessions on NFS without getting rid of HTTP_Session2 calls. ;-)
If you deployed HTTP_Session2 as well, I'd like to hear from you. Contact me at till-at-php-dot-net, or comment. I am pretty sure that in terms of stability it's more than beta code since I use it myself and we sometimes push 4+ mbit of traffic on the site, but all feedback is welcome.
