I hereby claim:
- I am dustinsoftware on github.
- I am dustinmastersolo (https://keybase.io/dustinmastersolo) on keybase.
- I have a public key ASCr_gMAyZAGGVcPdqQw7MFTbrzPhUeqN-3wAxf8E-th_Qo
To claim this, I am signing this object:
using System; | |
using System.Linq; | |
using System.Net; | |
using System.Net.Sockets; | |
using System.Text; | |
using System.Threading; | |
namespace udptest | |
{ | |
class Program |
I hereby claim:
To claim this, I am signing this object:
Early draft, please don't publish until the performance improvements are merged and shipped.
React 16.5 recently shipped, which added support for some new Profiling tools. We recently used these tools to identify a major source of slow render performance.
Faithlife.com is a web application powered by React 16.3. The homepage consists of a reverse-chronological timeline of posts. We received some reports that interactions with posts (such as replying) caused the browser to lag, depending on how far down the post was on the page. The further down the page the post was, the more lag occurred.
After updating React to 16.5 on a local copy of Faithlife, our next step was to start profiling and capture what components were re-rendering. Below is a screenshot of what the tools showed us clicking the 'Like' button on any post:
At Faithlife, we've been using OAuth 1.0a to handle authentication between services. Instead of designing our apps as monoliths, we've been perferring to build lightweight frontend applications that call RESTful microservices, returning entities as JSON. These frontend applications don't touch our databases directly. Among other benefits, this allows us to better allocate hardware resources (CPU, RAM, disk) to applications that need them.
A typical request to Faithlife might look something like this:
![mermaid sequenceDiagram participant Frontend participant Accounts participant Community Newsfeed participant Amber API
using System; | |
using System.Linq; | |
using System.Net.Http; | |
using System.Reflection; | |
using System.Runtime.InteropServices; | |
using System.Threading.Tasks; | |
namespace HttpClientTest | |
{ | |
class Program |
Problem A - Increased latency:
/** | |
* Copyright (c) 2015, Facebook, Inc. | |
* All rights reserved. | |
* | |
* This source code is licensed under the BSD-style license found in the | |
* LICENSE file in the root directory of this source tree. An additional grant | |
* of patent rights can be found in the PATENTS file in the same directory. | |
*/ | |
import { Provider, connect } from 'react-redux'; |
title | published | description | tags | cover_image |
---|---|---|---|---|
Inspecting .NET application state with SOS |
false |
Learn how to use the Windows Debugger to inspect application state from a .NET process dump |
.net, windbg, csharp, debugging |
In this post, we'll cover how to use the SOS debugging tools to inspect variables from a process dump of a .NET Framework / .NET Core application.
title | published | description | tags | cover_image |
---|---|---|---|---|
Mitigating cross-site scripting with Content Security Policy |
false |
Learn how to use Content Security policy to defend your site against cross-site scripting attacks |
security, xss, javascript |
In this post, we're going to look at using Content Security Policy (CSP) as a defense-in-depth technique to block script injection attacks.
test |