A new way of writing HTML code using CSS-like selector syntax
This is a handy set of tools for high-speed HTML and CSS coding. It looks interesting…
This is a handy set of tools for high-speed HTML and CSS coding. It looks interesting…
You’re writing a live-updating web application. Maybe it’s some sort of chat, a multiplayer Flash game, a live feed reader, or maybe it’s a realtime HTCPCP teapot controller. Either way, you won’t have status updates come only when the user refreshes a page, and polling the server every couple of seconds seems to you ugly and insufficient. But you don’t quite want to commit to writing your application in any of the available asynchronous scripted web serverframeworks. You’re also not crazy about CometD, maybe because you think the Bayeux protocol is overkill.
Solution?
This module turns Nginx into an adept HTTP Push and Comet server. It takes care of all the connection juggling, and exposes a simple interface to broadcast messages to clients via plain old HTTP requests. This lets you write live-updating asynchronous web applications as easily as their oldschool classic counterparts, since your code does not need to manage requests with delayed responses.
NHPM fully implements the Basic HTTP Push Relay Protocol, a no-frills publisher/subscriber protocol centered on uniquely identifiable channels. It is an order of magnitude simpler and more basic than similar protocols (such asBayeux). However, this basic functionality together with the flexibility of the server configuration make it possible to reformulate most HTTP Push use cases in Basic HTTP Push Relay Protocol language with very little application- and client-side programming overhead.
Enjoy!
YouTube may pay less to be online than you do, a new report on internet connectivity suggests, calling into question a recent analysis arguing Google’s popular video service is bleeding money and demonstrating how the internet has continued to morph to fit user’s behavior.
In fact, with YouTube’s help, Google is now responsible for at least 6 percent of the internet’s traffic, and likely more — and may not be paying an ISP at all to serve up all that content and attached ads.

Credit Suisse made headlines this summer when it estimated that YouTube was binging on bandwidth, losing Google a half a billion dollars in 2009 as it streams 75 billion videos. But a new report from Arbor Networks suggests that Google’s traffic is approaching 10 percent of the net’s traffic, and that it’s got so much fiber optic cable, it is simply trading traffic, with no payment involved, with the net’s largest ISPs.
“I think Google’s transit costs are close to zero,” said Craig Labovitz, the chief scientist for Arbor Networks and a longtime internet researcher. Arbor Networks, which sells network monitoring equipment used by about 70 percent of the net’s ISPs, likely knows more about the net’s ebbs and flows than anyone outside of the National Security Agency.
And the extraordinary fact that a website serving nearly 100 billion videos a year has no bandwidth bill means the net isn’t the network it used to be.
The following screencast demonstrates how easy it is to develop asynchronous forms posting data which receiving back JASON data from the server by using some of the best frameworks out there, jQuery and CodeIgniter…
Reference: http://geekhut.org/2009/06/how-to-codeigniter-jquery-json/
Security is one of the most often-cited objections to cloud computing; analysts and skeptical companies ask “who would trust their essential data ‘out there’ somewhere?”.
The security issues involved in protecting clouds from outside threats are similar to those already facing large datacenters, except that responsibility is divided between the cloud user and the cloud operator. The cloud user is responsible for application-level security. The cloud provider is responsible for physical security, and likely for enforcing external firewall policies. Security for intermediate layers of the software stack is a shared between the user and the operator; the lower the level of abstraction exposed to the user, the more responsibility goes with it. Amazon EC2 users have more responsibility for their security than do Azure users, who in turn have more responsibilities than AppEngine customers. This user responsibility, in turn, can be outsourced to third parties who sell specialty security services. The homogeneity and standardized interfaces of platforms like EC2 makes it possible for a company to offer, say, configuration management or firewall rule analysis as value-added services. Outsourced IT is familiar in the enterprise world; there is nothing intrinsicaly infeasible about trusting third parties with essential corporate infrastructure.
While cloud computing may make external-facing security easier, it does pose the new problem of internal-facing security. Cloud providers need to guard against theft or denial of service attacks by users. Users need to be protected against one another.
The primary security mechanism in today’s clouds is virtualization. This is a powerful defense, and protects against most attempts by users to attack one another or the underlying cloud infrastructure. However, not all resources are virtualized and not all virtualizion environments are bug-free. Virtualization software has been known to contain bugs that allow virtualized code to “break loose” to some extent. [1] Incorrect network virtualization may allow user code access to sensitive portions of the provider’s infrastructure, or to the resources of other users. These challenges, though, are similar to those involved in mangaging large non-cloud datacenters, where different applications need to be protected from one another. Any large internet service will need to ensure that one buggy service doesn’t take down the entire datacenter, or that a single security hole doesn’t compromise everything else.
One last security concern is protecting the cloud user against the provider. The provider will by definition control the “bottom layer” of the software stack, which effectively circumvents most known security techniques. Absent radical changes in security technology, we expect that users will use contracts and courts, rather than clever security engineering, to guard against provider malfeasence. The one important exception is the risk of inadvertent data loss. It’s hard to imagine Amazon spying on the contents of virtual machine memory; it’s easy to imagine a hard disk being disposed of without being wiped, or a permissions bug making data visible improperly.
There’s an obvious defense, namely user-level encryption of storage. This is already common for high-value data outside the cloud, and both tools and expertise are readily available. The catch is that key management is still challenging: users would need to be careful that the keys are never stored on permanent storage or handled improperly. Providers could make this simpler by exposing APIs for things like curtained memory or security sensive storage that should never be paged out.
[1] Indeed, even correct VM environments can allow the virtualized software to “escape” in the presence of hardware errors. See Sudhakar Govindavajhala and Andrew W. Appel, Using Memory Errors to Attack a Virtual Machine. 2003 IEEE Symposium on Security and Privacy, pp. 154-165, May 2003.
Google has released O3D, a browser plugin that gives developers a 3D API. It sits at a slightly higher level than other APIs (such as OpenGL / Canvas 3D type implementations) so it will be interesting to see if developers like the higher level abstraction, especially for building games. These APIs can also be implemented on top of the lower level APIs, so in theory it could sit on top of Canvas 3D.
There are plenty of demos, samples of code and shaders (they created a O3D shading language).
Interestingly, it embeds V8 as the JavaScript engine which makes for a uniform engine, but unfortunately you can’t use your browser debugger (e.g. no Firebug).
It has also been carefully positioned “This API is shared at an early stage as part of a conversation with the broader developer community about establishing an open web standard for 3D graphics.”
It is interesting to see another new plugin from Google. I always hoped that Gears would be one developer plugin to rule them all but then we have the Earth API, and this (as well as the non developer ones like the defunct Lively).
Anyway, cool to see rich experiments in bringing 3D to Web developers, and I look forward to seeing what people do with it! Leisure Suit Larry 3D anyone?
Yes, in my opinion PHP is still one of the best solution to build complex web 2.0 applications.
There are a lot of great PHP Frameworks out there which makes your life easier (Symfony, CakePHP, Codeigniter, and more…).
Now you can enjoy 100% Object-relational mapping in PHP by using IgnitedRecord library under the Codeigniter framework.
Here is a snapshot of how ORM can be achieved with PHP:
$this->load->model(‘ignitedrecord/ignitedrecord’);
$this->post = IgnitedRecord::factory(‘posts’);
$this->post->belongs_to(‘user’)->fk(‘author’);
$posts = $this->post->like(‘CodeIgniter’)
->order_by(‘date’, ‘desc’)
->join_related(‘user’)
->find_all();
foreach($posts as $post){
echo $post->title;
echo $post->user_username;
}
I was amazed when I saw that the iPhone provides a unix-like terminal.
I read this article: http://www.mgamble.ca/oss/iphone_asterisk/ and I realized that asterisk PBX can run on this mobile and handle calls as a typical call center with welcoming messages, ques, rules and so on…
What else could we expect? web server running on the mobile? This is possible too!
Check this out: http://idude.org/2007/11/07/an-iphone-powered-apache-web-server-with-php/
This underground data center has greenhouses, waterfalls, German submarine engines, simulated daylight and can withstand a hit from a hydrogen bomb. It looks like the secret HQ of a James Bond villain.
And it is real. It is a newly opened high-security data center run by one of Sweden’s largest ISPs, located in an old nuclear bunker deep below the bedrock of Stockholm city, sealed off from the world by entrance doors 40 cm thick (almost 16 inches).

Above left: View from the conference room (its floor is the surface of the Moon). Above right: Power equipment.

Above: The NOC is set in a cozy jungle setting. That light fog almost makes us think of cloud computing. Fog computing?

Above left: The submarine engines used for backup power. Above right: Another view of the power equipment.
Further info: http://www.bahnhof.se/colocation.php