dotnetomaniak.pl

Strona głównaUżytkownik

tpeczek | użytkownik

tpeczek
tpeczek
420,15
12 godzin, 40 minut temu
6 grudnia, 2016
dotnetomaniak.pl

WebSocket is the closest API to a network socket available in browser. This makes it probably the most flexible transport which a web application can use. That flexibility comes at price. From WebSocket perspective the message content is opaque. This means that client and server must agree on application subprotocol. WebSocket provides a simple subprotocol negotiation mechanism which helps in that task.

[EN] WebSocket subprotocol negotiation in ASP.NET Core

Web 23 czerwca 2017 09:40:11 GMT tpeczek 28 spam? rozwiń

There is a number of Web APIs which allow measuring performance of web applications. The youngest member of that family is Server Timing API which allows communicating the server performance metrics to the client. This article shows how this API can be used in ASP.NET Core.

Źródło: www.tpeczek.com
Dziel się z innymi:
[EN] Feeding Server Timing API from ASP.NET Core

Web 10 dni, 4 godziny, 2 minuty temu tpeczek 46 rozwiń

On of the hardest parts of getting an open source project into state which allows others to use it effectively is creating documentation. This post shows how you can generate documentation directly from source code by using DocFx.

Źródło: www.tpeczek.com
Dziel się z innymi:
[EN] Generating documentation with DocFX as part of VS solution

Inne 31 dni, 9 godzin, 45 minut temu tpeczek 35 rozwiń

Google's Certificate Transparency project is an open framework for monitoring and auditing SSL certificates. Starting April 2018 Chrome will require compliance with Certificate Transparency. Expect-CT Extension for HTTP will introduce a way to test the Certificate Transparency policy and this article shows how it can be used once it arrives.

Źródło: www.tpeczek.com
Dziel się z innymi:
[EN] Preparing for Chrome's Certificate Transparency policy - Expect-CT with reporting in ASP.​NET Core

Web 47 dni, 19 godzin, 12 minut temu tpeczek 17 rozwiń

ASP.NET Core comes with ready to use Cross Origin Resource Sharing support. The usage is very straightforward and nicely described in documentation, but what if there is a need to reconfigure the policy at runtime?

Źródło: www.tpeczek.com
Dziel się z innymi:
[EN] Reconfiguring CORS policy in ASP.NET Core at runtime

Web 26 kwietnia 2017 07:24:37 GMT tpeczek 20 spam? rozwiń

Recently I've been playing a lot with HTTP/2 and with ASP.NET Core but I didn't had chance to play with both at once. I've decided it's time to change that. Unfortunately the direct HTTP/2 support for Kestrel is still in backlog. Luckily Kestrel is not the only HTTP server implementation for ASP.NET Core.

Źródło: www.tpeczek.com
Dziel się z innymi:
[EN] HTTP/2 with Server Push proof of concept for ASP.NET Core HttpSysServer

Web 80 dni, 18 godzin, 49 minut temu tpeczek 42 rozwiń

The amount of transferred data matters. On one hand it often contributes to the cost of running a service and on the other a lot of clients doesn't have as fast connections as we would like to believe. This is why response compression is one of key performance mechanisms in web world.

[EN] Extending ASP.NET Core response compression with support for Brotli

Web 98 dni, 7 godzin, 14 minut temu tpeczek 16 rozwiń

In previous post I've shown how HttpClient can be extended with payload encryption capabilities by providing support for aes128gcm encoding. In this post I'm going to extend Aes128GcmEncoding class with decoding capabilities.

Dziel się z innymi:
[EN] Supporting Encrypted Content-Encoding in HttpClient (Part 2 of 2) - Decoding

Web 7 marca 2017 21:58:27 GMT tpeczek 8 spam? rozwiń

The "Encrypted Content-Encoding for HTTP" aims at providing standard solution for encrypting the contents of a HTTP message so that when the payload is stored, only someone with the appropriate key can read it. In this and next post I'm going to show how it can be used with HttpClient.

Dziel się z innymi:
[EN] Supporting Encrypted Content-Encoding in HttpClient (Part 1 of 2) - Encoding

Web 117 dni, 8 godzin, 20 minut temu tpeczek 40 rozwiń

The web socket protocol is currently the most popular one for pushing data to browsers, however it's not the only one. The Server-Sent Events (SSE) is a very interesting alternative which can provide better performance for specific use cases. In this post I'm going to show it can be used with ASP.NET Core.

[EN] Server-Sent Events (SSE) support for ASP.NET Core

Web 132 dni, 8 godzin, 55 minut temu tpeczek 117 rozwiń

This is one of those "I had to explain this couple times already so next time I want something I can redirect people to" kind of post. What I want to write about is difference in behavior between using new() and DbSet.Create() for instantiating new entities.

Dziel się z innymi:
[EN] Entity Framework - new() vs DbSet.Create()

Inne 140 dni, 6 godzin, 10 minut temu tpeczek 202 rozwiń

This is a follow up to my previous post on HTTP/2 Server Push which deep dives into subject of client side caching and explores the Cache Digest proposal.

Dziel się z innymi:
[EN] HTTP/2 Server Push and ASP.NET MVC - Cache Digest

Web 164 dni, 8 godzin, 52 minuty temu tpeczek 81 rozwiń

In previous post I've shown how a temporary table can be generated based on IQueryable and then reused in subsequent queries. I have also pointed out a serious limitation. The goal of this post is to address that limitation and touch on unit testing aspect.

Dziel się z innymi:
[EN] Entity Framework 6 - Dynamically creating temporary tables from IQueryable (Part 2 of 2)

Inne 171 dni, 15 godzin, 25 minut temu tpeczek 140 rozwiń

One of the new features in HTTP/2 is Server Push. It allows the server to send resources to the browser without having to wait for the browser to request it. I don't intend to provide comprehensive information regarding HTTP/2 Server Push here as there is a lot of resources on the web doing that already, all I want is to play a little with Server Push in context of ASP.NET MVC.

Dziel się z innymi:
[EN] HTTP/2 Server Push and ASP.NET MVC

Web 185 dni, 14 godzin, 17 minut temu tpeczek 112 rozwiń

Some time ago I've written about HtmlHelper providing support for Content Security Policy. The solution presented worked well, but it required quite nasty markup. With ASP.NET Core MVC there is a new tool for this kind of tasks - TagHelpers.

Tagi: Asp.Net Core, CSP
Dziel się z innymi:
[EN] Content Security Policy in ASP.NET Core MVC - TagHelper

Inne 195 dni, 18 godzin, 13 minut temu tpeczek 66 rozwiń

I'm a huge fan of entity based and result set based relational mapping (classic ORMs). I'm also huge fan of DML based relational mapping (micro ORMs). In general I'm a huge fan of every technology that allows me to get the job done in the best possible way. I believe that one should never limit himself to single approach within a project - it should always be about choosing the best tool for the job. But sometimes there are real life constraints (licensing, business, politics etc.) which are limiting the...

Dziel się z innymi:
[EN] Entity Framework 6 - Dynamically creating temporary tables from IQueryable (Part 1 of 2)

Inne 195 dni, 18 godzin, 13 minut temu tpeczek 189 rozwiń

Szkolenia SecurITum

październik

Zobacz wszystkie

Najaktywniejsi

1

macko (32 816,53)

2

http://pawlos.blo... (31 626,47)

3

pzielinski (27 178,29)

4

gordon_shumway (21 178,87)

5

paduda (20 336,33)

6

psz750 (13 018,14)

7

rroszczyk (10 386,15)

8

Damian (9 056,1)

9

danielplawgo (7 235,99)

10

arek (6 807,95)

11

burczu (6 214,22)

12

PaSkol (5 393,84)

13

lukaszgasior (4 097,38)

14

jj09 (3 608,06)

15

jedmac (3 318,39)

16

http://jakub-flor... (3 224,66)

17

spetz (3 078,27)

18

CaMeL (2 954,87)

19

lkurzyniec (2 633,85)

20

mnikolajuk (2 596,93)