From 82d15aedc031d01e9909fe2d41f8e299cd8b3fda Mon Sep 17 00:00:00 2001 From: Bernhard Miklautz Date: Thu, 12 Nov 2020 12:00:36 +0100 Subject: fix: html tag in blog post --- _posts/2020-11-09-hi-myrtille.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/_posts/2020-11-09-hi-myrtille.md b/_posts/2020-11-09-hi-myrtille.md index 72d8790..785d4ed 100644 --- a/_posts/2020-11-09-hi-myrtille.md +++ b/_posts/2020-11-09-hi-myrtille.md @@ -46,9 +46,9 @@ Responsiveness is the key to a good user experience. I tried hard to chase for e Whenever possible, I try to parallelize the processing. The user inputs and display updates, for example, are asynchronous. You can have a display change resulting from a user action, or not. What is important however, is to maintain the order in which they occur. I decided to use named pipes between the gateway and FreeRDP, because they are FIFO queues and maintain such an order. XmlHttp requests and websocket messages are also delivered in order, and so are long polling DOM injections and server-sent events (SSE). -A path for improvement would be to use hardware accelerated graphics and take advantage of the H.264/AVC encoding supported by FreeRDP. Myrtille actually relies on images (PNG/JPEG/WEBP), generated by GDI+ (win32 API, software), but this could be replaced by a video stream (MP4/OGG/WEBM, etc.), generated by FreeRDP (against hardware, or software when using a VM), and pushed from the gateway to the browser into an HTML5