Re: [Patch] Support HTTP/2 in HTTP client

. However, sometime during all of this I figured out how to get the system-installed extensions working with my personal build of Guile, so the TLS extension now works and I can cut Curl out of this code and just use “http-head”. We can drop this patch. Thanks, Derek Derek Upham writes: I made

Re: [Patch] Support HTTP/2 in HTTP client

support it, guile's client should only be offering http/1.1 to the server. On Tue, 31 Mar 2020 at 15:49, Derek Upham wrote: Companies like Google now respond to HTTP requests with HTTP 2. For example: curl --silent --head https://www.google.com returns the first line HTTP/2 200 The

[Patch] Handle all four etags types in HTTP client

. This patch updates the parsing code to recognize and handle that case. >From dfd68f4f2dc6c2b3b86191e550a50a19533522d3 Mon Sep 17 00:00:00 2001 From: Derek Upham Date: Sun, 19 Jan 2020 16:55:10 -0800 Subject: [PATCH 2/2] Properly handle unquoted and quoted etags. --- module/web/http.

[Patch] Support HTTP/2 in HTTP client

” on input and output. HTTP version numbers don’t proliferate quickly, so the code uses a brute force approach for now. >From 97d82f131afb40527340fb7126efaf50f7fe59eb Mon Sep 17 00:00:00 2001 From: Derek Upham Date: Tue, 4 Jul 2017 08:54:06 -0700 Subject: [PATCH 1/2] Support HTTP/2 headers f

[PATCH] Support HTTP/2 headers from web servers.

>From f957bd2b496a2aea92d1184e57c18215acc3ed22 Mon Sep 17 00:00:00 2001 From: Derek Upham Date: Tue, 4 Jul 2017 08:54:06 -0700 Subject: [PATCH] Support HTTP/2 headers from web servers. For example, curl --silent --head https://www.google.com returns the first line HTTP/2 200 which d

[PATCH] Support HTTP/2 headers from web servers.

I’m tempted to drop the whole “find the dot index” approach for HTTP/1.x and just explicitly match on “HTTP/1.0” and “HTTP/1.1” as well. Derek >From f957bd2b496a2aea92d1184e57c18215acc3ed22 Mon Sep 17 00:00:00 2001 From: Derek Upham Date: Tue, 4 Jul 2017 08:54:06 -0700 Subject: [PATCH] Suppor

Re: feature request: process creation

ould be > improved perhaps. just something i have read about > (https://stackoverflow.com/questions/899038/getting-the-highest-allocated-file-descriptor > ): it gets the maximum number of file descriptors soft limit (which might > have been lowered at some point) using the linux specific getrlimit and 1024 > if that is not available (can't there be file descriptors above 1024?). -- Derek Upham s...@blarg.net

Re: Cygwin port of Guile 2.2

that accurate? We can also update stop_finalization_thread to use the new scm_i_pthread_join. Unfortunately, I think the GC threads are going to end up being immovable objects in the path to full process-form support. Derek -- Derek Upham s...@blarg.net

Re: Cygwin port of Guile 2.2

tantial evidence, but it’s suggestive. 2. In the first successful case (first it the overall list), the finalizer cleanup doesn’t start until the signal delivery thread cleanup completes. There’s nothing at the code level enforcing that. I wonder whether there is a single, hidden, background thread that coordinates the cleanup. That’s pure speculation. Derek -- Derek Upham s...@blarg.net

Re: Cygwin port of Guile 2.2

Andy Wingo writes: > On Mon 01 May 2017 22:48, Derek Upham writes: > >> Running pthread_join() on a thread only guarantees that the thread has >> returned an exit value. > > Would you mind providing a reference please? It is not that I don't > believe you bu

Re: Cygwin port of Guile 2.2

Derek Upham writes: >> I think also that if you are most interested in a system in which >> primitive-fork plays a large role, then probably you want a Guile >> without threads (including the GC mark threads). Threads + fork is not >> a recipe for success :) > >

Re: Cygwin port of Guile 2.2

o the garbage collector, so it avoids this problem; it can have pathological edge cases for long-running programs, however.) Derek -- Derek Upham s...@blarg.net

Re: Cygwin port of Guile 2.2

he finalizer thread and support SCSH-style (begin ...) process forms. Shutting down the finalizer thread is the best we can do. All of this is on GNU/Linux, of course, not Cygwin. Derek -- Derek Upham s...@blarg.net

Re: [PATCH] Throw an exception when mutating read-only data

save/restore mechanisms. For example, scm_restore_signals won’t re-establish that handler. Derek -- Derek Upham s...@blarg.net

SCSH process forms and the signal delivery thread

, so shutting down the finalizer in the child is the best we can do. Is it worth restarting just the parent's finalizer thread after forking? Other, independent, cleanup opportunities: - The docs for "primitive-fork" need to mention that calling "primitive-fork" shuts down finalizers for the parent and the child. - Calling “restore-signals” should stop any running signal delivery thread, to bring Guile back to a consistent state. Thanks, Derek -- Derek Upham s...@blarg.net