dyoder

6 ms·

91.
Everything Has Changed(pandastrike.com)
1 points by dyoder 12y ago|0 comments
92.
HTTP Made Simple(pandastrike.com)
2 points by dyoder 12y ago|2 comments
93.
Browser-Based N-Body Simulator in CoffeeScript(nbody.pandastrike.com)
2 points by dyoder 12y ago|1 comments
94.
The Emerging (Security) Threat to Satellite Communications(threatpost.com)
1 points by dyoder 12y ago|0 comments
95.
by dyoder 12y ago
> ...it's just an API failure This. As far as the bandwidth issue goes, effective use of caching and compression can go a long way. Schemes varying the responses via the URL compromise schema validation based on media type (see JSON
96.
Maryland dealer will sell nation’s first smart gun(washingtonpost.com)
2 points by dyoder 12y ago|0 comments
97.
by dyoder 12y ago
Very interesting. I was thinking something similar could be done in Haskell.
98.
TLS/SSL implementation in Haskell(github.com)
231 points by dyoder 12y ago|176 comments
99.
View and analyze thousands of exploited websites.(threatglass.com)
2 points by dyoder 13y ago|0 comments
100.
by dyoder 13y ago
The negative response to this post is over the top. At most, you can say that they overstated their case by neglecting to talk about server trust and using the word "comfortable" in an article about security. :) To address a few r
101.
by dyoder 13y ago
make sure your login and signup are via HTTPS before you go much further.
102.
by dyoder 14y ago
You get 'windowed queries into the channel history for free' on spire.io as well.
103.
by dyoder 14y ago
FWIW, we use HTTP as intended, not to tunnel RPCs.
104.
by dyoder 14y ago
Correct. We do not yet work well offline. Request buffering, data storage, and synchronization are on our roadmap.
105.
by dyoder 14y ago
Also, you can implement data synchronization over a messaging layer but not the other way around. So I'd say our approach is actually more flexible. And we do plan to introduce APIs to make data synchronization easier.
106.
by dyoder 15y ago
Wasn't aware of it, actually. Thanks for mentioning it. Looks very interesting. I'll also amend the blog post.
107.
Request for comments: capability security for Web applications(spire.io)
12 points by dyoder 15y ago|3 comments
108.
by dyoder 15y ago
Nailed it. Composite resources and good use of caching with fine-grained resources can go a long way. HTTP is a pretty sophisticated protocol, when all is said and done. That means there is a learning curve in using it effectively. However,
109.
by dyoder 15y ago
We use CORS at spire.io.
110.
by dyoder 15y ago
Thanks for your suggestion, Matthew. We do anticipate some applications wanting more than one instance. There are two scenarios where this comes up. 1. You want separate connections per instance. This is useful in load testing, among other
111.
The Death Ray And The Lean Startup(borderstylo.com)
2 points by dyoder 16y ago|0 comments