Pusher sur Twitter : "pusher-js 3.0 released. Now in NPM to enable easier use with #browserify, #webpack and #jspm. Js 3.0.0 released. It’s been a while since we released a major version of pusher-js. In this release we’ve completely removed the Flash transport mechanism – requiring the major version bump – and added a UMD wrapper to the built library making it easier to use pusher-js with modern JavaScript tools.
Flash Fallback Removed Back in 2010 we offered native WebSocket support and used an in-browser Flash proxy fallback mechanism for older browsers called web-socket-js. In 2013 we released 2.0.0 and added multiple HTTP-based fallback options. In 3.0 we are removing the legacy Flash fallback. Right now connections via Flash represent only 0.2% of all our connections and we hope to get this down to 0 by the end of the year. UMD wrapper & published to NPM In order to support modern JavaScript development practices we’ve added a UMD (Universal Module Definition) wrapper to pusher-js and published pusher-js to NPM.
This means you can write code as follows where you can require('pusher-js'): Help us improve our libraries. Pusher sur Twitter : "pusher-js 3.0.0 released. Say goodbye to legacy Flash fallback and hello to pusher-js in NPM. Adam Morgan sur Twitter : "Fully agree with @maxthelion - @pusher #CEO #RealtimeAsStandard #apps #web #notifications... Home – Future of Web Apps 2015. Review of Realtime Web Tech Predictions from 2014 - Phil Leggetter - Real-Time Web Software & Developer Evangelist. Phil Leggetter sur Twitter : "If you ever do any development with #WebHooks. You *have to* use @runscope. Passageway CLI + Web Dashboard FTW. Components: Introduction. Thoughts from ForwardJS. ForwardJS took place in San Francisco last week.
It was a great event consisting of progressive workshops and talks. Here's a post covering our involvement and the things I found most interesting: FluxJS, ES6 and Web Components. Building Large JS Apps Workshop On the day before the main event I ran a workshop covering How to Build Large Front-End Apps that Scale. By "scale" I mean grow in a maintainable way. The workshop covers principles and practices that help this take place and we use the BladeRunnerJS toolkit to help demonstrate these. I've had some feedback from the workshop already and it seemed to go down really well.
Facebook's FluxJS One of the core takeaways from the workshop should be the importance of building applications in consistent ways; if this application is going to stand the test of time it needs to be as easy as possible for anybody to pick up, extend and maintain the codebase. Bill Fisher and Jing Chen spoke at ForwardJS about FluxJS. ES6 Modules & HTTP2. The Future of AngularJS. PubNub Real-Time WebGL Visualization. Syd Lawrence - The "Interne... on Livestream. My Dublin Web Summit Talk - Enabling and Celebrating The Doers. I gave a new talk on the Digital Marketing stage at Dublin Web Summit this week.
It was called Enabling and Celebrating The Doers. It was only a 15 minute slot, but the theme was to take a quick peak at the developer community; its size, make up, and what it produces. Then dip into the playbook of some of the companies doing a good job of engaging with it. Finally wrapping up with some ideas on how to celebrate the individuals that create awesome things with your tools. WebRTC comes to Firefox. As we mentioned in the Hacks blog back in April , WebRTC will be on by default in Firefox 22. getUserMedia (gUM) has been on by default since Firefox 20. PeerConnection and DataChannel, which enable video/audio calling and peer-to-peer data sharing, are what’s new in Firefox 22 (due to be released today). WebRTC brings real-time communication to the web for the first time ever, and we’re excited to get this new technology into the hands of developers.
We believe the industry has only scratched the surface of what’s possible with WebRTC, and only by getting it into the hands of developers and early adopters will we see this technology’s true potential. Known issues/limitations There are a few known issues/limitations in the early releases: We are initially focused on getting 1:1 calling working well. Trying WebRTC support today If you’d like to try out Firefox’s WebRTC support today, here are some sites that support WebRTC calling: NOTE: most of these sites support 3 or more callers. 12 Million Concurrent Connections with MigratoryData WebSocket Server | Building Scalable Real-Time Websites. We have recently completed a new performance benchmark which demonstrates that MigratoryData WebSocket Server is able to handle 12 million concurrent users from a single server Dell PowerEdge R610 while pushing a substantial amount of live data (1.015 gigabit per second).
This benchmark scenario shows that MigratoryData WebSocket Server is ideal for infrastructures delivering real-time data to a huge number of users, especially for mobile push notifications infrastructures that are typically demanded by telecom customers with tens of millions users. In this benchmark scenario, MigratoryData scales up to 12 million concurrent users from a single Dell PowerEdge R610 server while pushing up to 1.015 Gbps live data (each user receives a 512-byte message every minute). The CPU utilization diagram below shows that MigratoryData WebSocket Server scales linearly with the hardware. According to the chart above, MigratoryData uses only 57% CPU to handle 12 million users. Browsermeeting.com | A fastlane to a plugin free video conference using WebRTC. Integrating Pusher with Ember - Livsey.org. 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: First of all, lets define a Pusher object which will handle subscribing and unsubscribing to channels, and dispatches any messages we receive from Pusher to the router: Most of that is pretty straight-forward, we’re just wrapping some basic Pusher functionality and listening for any message which we get sent. There’s no longer a global App.router we can access in Ember, so we need to get the router from the container, then we simply pass send the event and data we got from Pusher. ViziCities Dev Diary #1: SimCity-like 3D Visualisation of Real Cities using WebGL : SimCity. Live Development with Brackets (experimental) – Brackets. As you all know and love, Brackets gives you immediate feedback in the browser when editing CSS files through the live preview.
We call this “live development”. What you did not know is that Brackets already includes some experimental features that allow the live development of HTML and JavaScript files. The video below demonstrates what I mean (best viewed in 720p): So, how does it work? For the live preview, we open a remote debugger connection to Chrome, which we can use to inspect and interact with the visible page. The live preview remote debugger connection can be used by extensions to do cool things. The connection is fairly easy to use and documented (see brackets/src/LiveDevelopment/Inspector/inspector.html) or the official (but incomplete) documentation. Nymgzsqmj Shared by leggetter. Event handling - Should WebSocket.onclose be triggered by user navigation or refresh.
Using WebSockets to control your TV backlight · leggetter. Network programming - WebSocket Client in Lua. MSDN Flash. CometD 2.4.0 WebSocket Benchmarks | Webtide Blogs. 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. We conducted several benchmarks using the CometD load tools on Amazon EC2 instances. HTTP Benchmark Results Below you can find the benchmark result graph when using the CometD long-polling transport, based on plain HTTP. Dev.w3.org Is Down. Windows Developer Preview: The Third IE10 Platform Preview - IEBlog. Blogs. 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. There are literally thousands of apps built leveraging PhoneGap across all of the phone platforms available today. The sessions available in this course are as follows:
Q&A: Are WebSockets ready for commercial use? Q&A: Are WebSockets ready for commercial use? What came before WebSockets? 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. It was conceived to be a collection of HyperText Markup Language (HTML) pages linking to one another to form a conceptual web of information.
Over time the static resources increased in number and richer items, such as images, began to be part of the web fabric. Soon there was a requirement for the Internet client, the web browser, to be more dynamic, for it to offer a richer experience. How do I cause the web browser to complete the loading process, although I am running pending AJAX requests in the background.
Free SEO Analysis - Pear Analytics Website Analyzer. 10 Years of Push Technology, Comet, and WebSockets. Internet Explorer 10 Platform Preview: About. Purpose The Internet Explorer 10 Guide for Developers provides a look at the developer features included in Internet Explorer 10, as well as the latest HTML5, JavaScript, and Cascading Style Sheets, Level 3 (CSS3) features available to developers of Windows Store apps using JavaScript for Windows 8. By using the documentation and samples in this guide, developers and designers can take full advantage of these new features. Important The contents of this guide apply to both Internet Explorer 10 and Windows Store apps using JavaScript for Windows 8, except where noted. Listed here are new developer features for Internet Explorer 10. In addition to reading the guide, be sure to see the Release Notes for installation information and known issues, as well as the Internet Explorer Test Drive site for new demos and examples.
Internet Explorer 10—as well as Windows Store apps using JavaScript—contains support for the following developer features. Developer audience. Blogs. Recent article in .net magazine: WebSockets – Code a real-time survey. C# - HTML5 WebSockets usage from .NET. HTML5, Websockets & the Mobile Web. Http - Why isn't BOSH more popular, especially as an alternative to WebSockets and long-polling. Dundee Web Standards – Fleet Collective and Browser Warfare. Real-time web platform with a focus on social media enabling websites.
Web2.0. Programming. Are My Sites Up? Future Of Web Apps - London 2008. 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. The Future of Web Apps The Future of Web Apps is a conference for web developers and entrepreneurs. Upcoming Events The Future of Web Design The Future of Web Design is a conference for web designers who are looking to learn new skills and meet like-minded people.
The Future of Mobile The Future of Mobile is a conference aimed at mobile designers, developers, and entrepreneurs. Chirp.