Get flash to fully experience Pearltrees
The Ember Router takes events from user actions and hands them off to the appropriate Route depending on where the user is within the app. Pusher receives events from your server which your app then handles, but you might want to do different things depending on where your user is within your app at the time the message is received. Wouldn’t it be great if we could hook these two things up together? Here’s what we’re going to end up with in a route:
Dear MSDN UK Flash Reader In this fortnight’s MSDN Flash newsletter we’re taking a look at one of the many exciting new technologies emerging for Web Developers - WebSockets. In the technical article below, Phil provides a great introduction to WebSockets and how they extend the ability of a standards-based client (usually a web-browser) to take part in full-duplex communications with an HTTP server. For me this is just one example of a number of areas where we're seeing the standards-based client reach out into the space traditionally occupied by a "native" client. The line between the two approaches is increasingly a blurry one and technologies like WebSockets and others like IndexedDB are part of that trend. You can find prototypes for these technologies for Internet Explorer in the HTML5 Labs .
Slightly more than one year has passed since the last CometD 2 benchmarks , and more than three years since the CometD 1 benchmark . During this year we have done a lot of work on CometD , both by adding features and by continuously improving performance and stability to make it faster and more scalable. With the upcoming CometD 2.4.0 release, one of the biggest changes is the implementation of a WebSocket transport for both the Java client and the Java server. The WebSocket protocol is finalizing at the IETF, major browsers all support various draft versions of the protocol (and Jetty supports all draft versions), so while WebSocket is slowly picking up, it is interesting to compare how WebSocket behaves with respect to HTTP for the typical scenarios that use CometD.
A few weeks ago, I wrote a post referencing how you as a developer don’t have to be torn between building mobile experiences in HTML5 or native phone apps. In fact, with the upcoming Mango release for Windows Phone, the “better together” story is a strong one that allows you to take advantage of great HTML5 goodness while harnessing that advantages that the native platform provides (like push notifications and live tiles) to create a full, rich experience for users and a manageable one for developers. To that end, I was very excited to learn that Nitobi , a great Vancouver-based company with a strong history in building mobile development platforms, has announced the release a beta of its popular PhoneGap framework supporting Mango . This is a really big deal , not only for Microsoft, but for you as a mobile developer.
With the arrival of WebSockets we finally have a standardised technology for true realtime bi-directional communication between a server and a web browser (or any other client). When we were creating our What are WebSockets? page we decided to write up a history of the technologies that came before and that are in some cases still in use today. How did we (developers) achieve realtime browser push before WebSockets and what were the downfalls of those technologies which meant they never really became mainstream? Here’s that write-up. The Internet wasn’t originally built to be all that dynamic.
We produce events that bring the web community together to learn, converse & connect. We run world-wide events for web professionals. Our goal is to inspire and help you turn your ideas into a reality. No matter if you’re a developer, designer or entrepreneur, we have an event for you.