Powered by Twitter Tools.
Just posted over at the Source Updates page is hopefully the final update to the MAME 0.125 dev cycle. It’s been a long road! Now is the time to check this out and ensure that all your favorites are still in fine working order before we lock down for MAME 0.126.
Powered by Twitter Tools.
The Service Pack Roll v5.0.1 for i386 and x86_64 architectures is released.
This roll includes the following fixes:
Detailed descriptions of the included fixes can be found here.
This roll can be installed onto a running frontend (neither reinstallation nor reboot is required).
ISO images for the Service Pack Roll can be found on the Downloads page.
Installation instructions can be found here.
Why are the best technical books also the thinnest? To make the case, I highly recommend the MySQL 5.1 Cluster Certification Study Guide In rack units, it’s a 1U; it fits nicely into my laptop bag; and if you’re considering implementing MySQL Cluster, it can save you a world of time.
Of course, if you get the book, you should consider the certification itself. There’s a legitimate debate about the usefulness of certification exams, but the MySQL 5.1 Cluster certification is a little more important than others for a couple of reasons:
1. In case you haven’t heard it by now, Cluster isn’t always the best fit. In many cases, an active/passive failover setup is a much more flexible and cost-effective approach. It’s not always a clear-cut decision. If you’re willing to make application changes and if you understand the internal workings of MySQL Cluster, it can be an amazing solution.
To see if cluster is a good fit, I recommend the following guides:
http://www.mysql.com/why-mysql/white-papers/mysql_cluster_eval_guide.php
http://www.mysql.com/why-mysql/white-papers/mysql_ha_solutions.php
2. There aren’t many consultants and DBA’s that have actually installed and used MySQL Cluster. There’s still a lot of misconceptions. The primary misconception is: “I know MySQL, I’m sure that I can quickly set it up and support a MySQL Cluster.” Outside of MySQL professional services group, there’s limited expertise in the marketplace. If someone has a MySQL Certification, at least you know that they’re tall enough for this ride.
I thought the most important part of the book was Chapter 7 regarding Indexes in NDB tables. Unless specifically suppressed, a hash and ordered (T-tree) index will be created for primary keys. The hash index is stored in the IndexMemory pool. The ordered index is stored in the DataMemory pool.
If you want to create a unique index, that’s a bit more complicated and it takes about a page to explain. Unique indexes have performance implications, which provides even more reason that someone should really understand MySQL internals before implementing a cluster.
To summarize, I’m hesitant to say this in public, but frankly; the study guide is a good read. It won’t make the Oprah book club any time soon, but it has some good discussions about hash indexing vs. t-tree indexes, database isolation levels, ACID properties and high availability concepts.
[sidenote: I usually rip technical books in half to achieve 1U. Usually, you can safely throw the first half away.]

Powered by Twitter Tools.
Phil and Greg were interviewed by Randal Schwartz and Leo Laporte for FLOSS Weekly 30. We talk about Rocks and clusters (and the Ada language!). Download the podcast and visit the TWiT web site:
The media got a little carried away with its praise of a recent federal court ruling that assigns certain privacy rights to text messages. The coverage, by and large, suggests that we’re on the verge of a revolution in workplace wireless communications that will see workers rise up and seize control of their electronic content. Sounds like fun. But it’s not gonna happen.
Why not? Because the ruling in Quon v. Arch Wireless Operating Co. is significant for some employees but less so for others. As for private employers, it might bear no significance at all.
Generally speaking, the Quon ruling says that wireless text messages are to be protected from unreasonable search and seizure, the same way handwritten letters are protected when sent in sealed envelopes through the postal service.
For Jeff Quon, a police sergeant in the small Southern California city of Ontario, the ruling meant vindication in a lawsuit against his employer. Quon had sued the city, its wireless carrier Arch and others for invading his privacy during an internal police investigation aimed at finding out how much Quon had used a two-way, government-issue pager to send personal, rather than work-related, messages.
Despite the limited scope of the Quon ruling, some parts of the decision speak broadly about the private nature of text messages and could serve to guide the court’s reasoning in future cases. And that is what the media coverage so far has focused on.
A CNET blogger said the ruling means employees’ text messages are now safe from their bosses’ prying eyes. The Los Angeles Times put a similar interpretation in a story headline: Your boss shouldn’t read your text or e-mail messages without an OK, court says. And The New York Times went so far as to say that Jeff Quon deserves a hearty thanks for taking the issue to court.
But while Quon’s courtroom victory might lend comfort to people who value privacy, it won’t necessarily dissuade private employers from snooping through employees’ wireless messages, because the constitutional protection against unreasonable search and seizure is pretty much limited to the government. In other words, you can’t use it against your IT manager or your HR department unless you’re a public employee.
You can’t use the Quon ruling against wireless carriers in all cases, either. The court’s conclusion hinges on a determination that Arch Wireless — now known as USA Mobility — held customers’ text messages in “electronic storage” under the Stored Communications Act of 1986. As such, the company violated federal law by disclosing transcripts of Quon’s text messages to the Ontario police department without his consent. Had the company not stored text messages after they were retrieved by users, it seems there would have been no internal investigation and perhaps no lawsuit. (For a more detailed analysis of the SCA, see the Electronic Frontier Foundation’s discussion of the case.)
It’s also unclear how the Ontario police department’s vague and inconsistent practice of regulating text messaging affected the outcome in Quon. The city had informal rules about text messaging on pagers, but no written policy.
Orin Kerr, a contributor to the Volokh Conspiracy law blog, warns that this lack of clarity could lead to some confusion. Clearly it already has. Personally, I’d like to agree with the conventional wisdom, that the court intends to let employees turn their company-issued wireless devices into little free speech stumps inside the virtual public square. It’s not hard to find blogs and news articles that suggest the law is pointing this way. But at least one employment lawyer has a different take. Philip Gordon, who specializes in privacy and data protection for Littler Mendelson, writes on his firm’s privacy blog that employers can easily and lawfully circumvent the Quon ruling, by setting and upholding policies that tell employees their text messages will be searched. If that strategy doesn’t work, I suspect employers will eventually find another one that does.

The debate around cloud computing and software-as-a-service (SaaS) has energized industry conversations on the future of software. But in fact what we are witnessing in the software industry today is not a revolution, but an evolution. Customers are most concerned with how to use software to sustain competitive advantage, align IT with the business and deliver the best experience for users without compromise — regardless of delivery option — whether that is SaaS, on-premise software or a combination of the two. That’s why this evolution of software in a services world is so important for the industry to broadly support, and why customers deserve more than all-or-nothing ultimatums. For more, see Refresh the Net.
Other infrastructure-themed stories that may be of interest:
The Long Tail of IT
Subscription Services: The Future of Our Entire Economy
Architecting for Failure
Five Nines is Still Not Enough
Do You Know What Kind of Cloud You’re Using?
Defogging Cloud Computing: A Taxonomy
The Craft: Automation and Scaling Infrastructure
Is Infrastructure the New Marketing Medium?
Achieving Equality is Critical to the Future of the Internet
Why Google Needs its Own Nuclear Plant
The Geography of Internet Infrastructure

Soon after the release of jQuery UI 1.5, we were getting many useful feedback and issues entered in our bugtracker. Today, we’re happy to release another version of jQuery UI which takes care of many minor regressions and a lot of unsolved issues.
1.5.1 doesn’t add any new features or API changes, but fixes more than 50 found issues. A full changelog is available, if you want to know the specifics. Updating to this version is highly recommended and likely not to break anything in your written code.
Additionally, issues within ThemeRoller and the demos on our homepage also have been reported and fixed. We are now continuing to finish all unit tests and functional demos, so expect to see another release of both UI and its website soon again.
You can grab the latest release as always via the downloader or as developer package at http://ui.jquery.com/download or if you prefer, get it as latest tag from Subversion.
See you soon,
Paul Bakaus & the jQuery UI Team