Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
leggetter
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
8 ms
·
31.
▲
by
leggetter
11y ago
It does seem to be the most commonly used WebSocket polyfill around. We also use web-socket-js [1] for fallback. But Version 3.0 of pusher-js [2] will remove that. One negative with SockJS has been the complexity of the fallback approach on
32.
▲
by
leggetter
11y ago
SockJS is definitely a reasonable choice as a base. At Pusher we use a fork of SockJS for HTTP fallback but we actually use em-websocket [1] (ruby) for our WebSocket API. Given the opportunity we'd probably move away from SockJS to som
33.
▲
by
leggetter
12y ago
This is definitely correct. The article focuses more on data synchronisation where as a lot of services (some of which jkarneges has highlighted) don't offer data storage and focus on letting you define your own feeds/channels
34.
▲
Domain Modelling Web Apps: An alternative approach to Grunt, Gulp and Broccoli.
(bladerunnerjs.org)
3 points
by
leggetter
12y ago
|
0 comments
35.
▲
by
leggetter
13y ago
We started doing this around 3 years ago. It's likely we'll change our default coding style from Node.js style to ES6 and our front-end components to Web Components - browser support pending. However, Web Components won't rem
36.
▲
by
leggetter
13y ago
yeah, we have focused on building dashboard like solutions. However, we're undergoing a number of mobile projects right now and we're hoping that part of open sourcing will result in trying to build other types of apps. Hopefully
37.
▲
by
leggetter
13y ago
It has come out of enterprise focused development - there's no getting away from that. And we have enterprise customers that the toolkit has to support. However, enterprise is in a state of convergence right now. Those that would not p
38.
▲
by
leggetter
13y ago
It's mainly a re-write of the older toolkit. Open sourcing has many benefits. As lead of the open sourcing initiative (not lead-dev) it's been an opportunity to re-evaluate what we're doing and a way to identify things that m
39.
▲
by
leggetter
13y ago
You could look at it that way. But I'd like it to align much more with Web Components and a defined architecture for inter-component (Blade) and service (shared resource e.g. back-end) communication. I think this comment best describes
40.
▲
by
leggetter
13y ago
Right now we use KnockoutJS in the Blade templates. the `data-bind=` syntax is from that. There's not reason you can't use another front-end UI binding library with a syntax that you prefer. This response provides more about why t
41.
▲
by
leggetter
13y ago
> Why call something a "blade" when you could call it a component or module for instance?it's just confusing and dont help understand what the framework is about. Naming things the right way is important.It means you got y
42.
▲
by
leggetter
13y ago
It was initially called "BladeRunner" and one of the main reasons we decided to rename it "BladeRunnerJS" was for Google. As with other JS-based solutions adding "JS" to the end clarifies it's for building
43.
▲
by
leggetter
13y ago
Yeah, thanks. Hopefully that's fixed now.
44.
▲
by
leggetter
13y ago
Ah, I understand now. See point 2 here: https://news.ycombinator.com/item?id=7297658
45.
▲
by
leggetter
13y ago
1. I guess I could've removed the "10" bit? 2. I'm running some realtime benchmarks on a number of hosted service providers. If I can get the geolocation it let's me add that to the benchmark results. Granted, a ban
46.
▲
by
leggetter
13y ago
No. That would be the geolocation API https://developer.mozilla.org/en/docs/WebAPI/Using_geolocati... You can of course use that in conjunction with realtime web technologies: For example, see: http:/&#
47.
▲
10 Realtime Web Technology Predictions for 2014
(leggetter.co.uk)
15 points
by
leggetter
13y ago
|
12 comments
48.
▲
by
leggetter
13y ago
Note: I work on the BladeRunnerJS team - the team behind Topiarist. I've created visualization tool using Topiarist and a service called yUML that creates a UML diagram showing the relationship between object definitions within a given
49.
▲
by
leggetter
13y ago
The thing that interests me most about this is the potential for changing configuration on-the-fly to deal internal or external network conditions, or simply from additional information extracted from the metrics. I don't know of any other
50.
▲
by
leggetter
13y ago
We've kept the FlashSocket option in there, as it ultimately means the user gets the benefit of a WebSocket connection without native WebSocket support; a single bidirectional connection resulting in the lowest latency possible. Our HTTP fa
51.
▲
Using Pusher to power cisimple’s real-time API
(blog.pusher.com)
6 points
by
leggetter
14y ago
|
0 comments
52.
▲
by
leggetter
14y ago
Blog post providing some details about the way Pusher was integrated http://blog.pusher.com/using-pusher-to-power-cisimples-real-...
53.
▲
by
leggetter
14y ago
It definitely makes sense to split the world up into multiple channels. That's what the guys who built http://wordsquared.com/ did. As you scroll you unsubscribe from channels that are out of view and subscribe to channels that are moving
54.
▲
by
leggetter
14y ago
http://reaDIYmate.com are pretty cool too.
55.
▲
by
leggetter
14y ago
Nice little example of the Internet of Things
56.
▲
Controlling a website on your desktop browser from your mobile using WebSockets
(blog.pusher.com)
1 points
by
leggetter
14y ago
|
0 comments
57.
▲
WebSockets realise Comet. They’re not an alternative.
(leggetter.co.uk)
1 points
by
leggetter
15y ago
|
0 comments
58.
▲
by
leggetter
15y ago
When it comes to nginx and apache you can always go down the hosted realtime infrastructure route. That way you can use WebSockets in your client (app) but you don't need to worry about installing mods or handling the persistent connections
59.
▲
by
leggetter
15y ago
Some expect Chrome for Android to become the default browser ( http://www.wired.com/gadgetlab/2012/02/chrome-android/ ) and if that happens the WebSockets will be supported. Firefox for Android also supports WebSockets. I can't 100% confirm
60.
▲
by
leggetter
15y ago
From my experience, working at Pusher and dealing with support for the past year, WebSockets do work over a mobile 3G connection when you use an SSL (wss://) connection. I tether (laptop -> mobile -> mobile data) quite a bit whilst
More ›