Red Hat and Rackspace Hosting have announced that they have won the dismissal of a patent suit by Uniloc USA. Uniloc was asserting patent #5,892,697, which relates to the handling of floating-point numbers. “In dismissing the case, Chief Judge Leonard Davis found that Uniloc’s claim was unpatentable under Supreme Court…
Go here to see the original:
Red Hat and Rackspace Face Down a Patent Troll
Kristian Høgsberg has proposed patches to Wayland and the Weston compositor for implementing pointer locks. Pointer locks allow for applications to lock the pointer so they receive relative inputs, which can improve the handling of some games running on Wayland…
Follow this link:
Pointer Lock Feature Proposed For Wayland
Fabien Potencier has new post post to the Symfony Blog today talking about a big update to the Symfony framework , the introduction of a new “fragment sub-framework”. This framework (now a part of the HttpKernel) allows the handling of requests based on a few different strategies. About a month ago, I merged a complete refactoring of the sub-requests management of Symfony. In fact, I created a whole new sub-framework to handle the rendering of resource fragments via different strategies. Besides classical master requests, the HttpKernel component is now able to handle sub-requests. Let’s me sum up the different strategies that are available: internal sub-requests, ESIs, HIncludes, and SSIs (in 2.3). He talks some about each strategy and what situations they’re best suited for and some sample code that shows the use of the “standalone” and “strategy” parameters. There’s also new methods you can call (like “render_esi” or “render_hinclude”) to work with the new features as well.
Go here to read the rest:
Symfony Blog: New in Symfony 2.2: The new fragment sub-framework
James Morris has an interesting new post to his site about the creation of a real-time web service that could be used for iOS applications via Websockets. He chose Ratchet for the handling (a PHP-based websocket tool) combined with Redis and Silex. I was approached by a betting/gambling development company who potentially needed a middleware building that would pull from an existing gambling web service and basically transmit to connected iPhone clients the changes from the web service. At first, the obvious answer might be to create another REST web service that the iPhone clients could just ping for changes. However, one of the devs explained that this wouldn’t be fast enough, or scale – they’d need changes to be transmitted as soon as possible, as the app would be a real-time betting app and there’d be thousands of connections to the server. His solution involved hooking together Ratchet, Redis, Silex and Predis-async to create this sample tool for handling the websocket requests. it uses the “pubsub”
Follow this link:
James Morris: A WebSockets, Ratchet, Silex and Redis PubSub Implementation
In a previous post of his Dave Marshall talked about using controllers as “services” in a Silex-based application. In this new post he takes it a step further and shows you how to use route helpers to make working with those controllers even simpler. Supposing we want to render some HTML, do we want to inject the template engine in to the controller? Should the controller be responsible for knowing how to render the template? I’m not sure, but if I can have it not do it with minimal fuss, I think I’d rather it not. The full stack framework has the @Template annotation, which allows developers to assign a template to a controller and then simply return an array. If they can do it in the full stack framework, we can do it in Silex. He includes the code for an example of a 404 handling page that uses the “convert” method to configure a route (path to a controller) for the currently matched route. He also shows the creation of a simple “CustomRoute” class and a “TemplateRenderingListener” to make it simpler to customize the handling and output of the request, all injected into the application’s DI …
More here:
Dave Marshall: Silex Route Helpers for a Cleaner Architecture