|
| 1 | +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> |
| 2 | +<HTML> |
| 3 | + <HEAD> |
| 4 | + <TITLE> [squid-dev] Architectural inquiry: Design rationale behind serialized request handling for identical URLs |
| 5 | + </TITLE> |
| 6 | + <LINK REL="Index" HREF="index.html" > |
| 7 | + <LINK REL="made" HREF="mailto:squid-dev%40lists.squid-cache.org?Subject=Re%3A%20%5Bsquid-dev%5D%20Architectural%20inquiry%3A%20Design%20rationale%20behind%0A%20serialized%20request%20handling%20for%20identical%20URLs&In-Reply-To=%3C6c0b53f8-7e71-4076-8f05-3eaffea872b7%40measurement-factory.com%3E"> |
| 8 | + <META NAME="robots" CONTENT="index,nofollow"> |
| 9 | + <style type="text/css"> |
| 10 | + pre { |
| 11 | + white-space: pre-wrap; /* css-2.1, curent FF, Opera, Safari */ |
| 12 | + } |
| 13 | + </style> |
| 14 | + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> |
| 15 | + <LINK REL="Previous" HREF="009977.html"> |
| 16 | + |
| 17 | + </HEAD> |
| 18 | + <BODY BGCOLOR="#ffffff"> |
| 19 | + <H1>[squid-dev] Architectural inquiry: Design rationale behind serialized request handling for identical URLs</H1> |
| 20 | + <B>Alex Rousskov</B> |
| 21 | + <A HREF="mailto:squid-dev%40lists.squid-cache.org?Subject=Re%3A%20%5Bsquid-dev%5D%20Architectural%20inquiry%3A%20Design%20rationale%20behind%0A%20serialized%20request%20handling%20for%20identical%20URLs&In-Reply-To=%3C6c0b53f8-7e71-4076-8f05-3eaffea872b7%40measurement-factory.com%3E" |
| 22 | + TITLE="[squid-dev] Architectural inquiry: Design rationale behind serialized request handling for identical URLs">rousskov at measurement-factory.com |
| 23 | + </A><BR> |
| 24 | + <I>Wed Feb 18 16:53:30 UTC 2026</I> |
| 25 | + <P><UL> |
| 26 | + <LI>Previous message (by thread): <A HREF="009977.html">[squid-dev] Architectural inquiry: Design rationale behind serialized request handling for identical URLs |
| 27 | +</A></li> |
| 28 | + |
| 29 | + <LI> <B>Messages sorted by:</B> |
| 30 | + <a href="date.html#9978">[ date ]</a> |
| 31 | + <a href="thread.html#9978">[ thread ]</a> |
| 32 | + <a href="subject.html#9978">[ subject ]</a> |
| 33 | + <a href="author.html#9978">[ author ]</a> |
| 34 | + </LI> |
| 35 | + </UL> |
| 36 | + <HR> |
| 37 | +<!--beginarticle--> |
| 38 | +<PRE>On 2026-02-18 05:59, ליאור בראון wrote: |
| 39 | + |
| 40 | +><i> I am currently working on a research project involving request |
| 41 | +</I>><i> dispatching and peer selection within the Squid-cache core. |
| 42 | +</I>><i> |
| 43 | +</I>><i> During my development, I have encountered several mechanisms and logic |
| 44 | +</I>><i> blocks within the source code that deliberately prevent or queue |
| 45 | +</I>><i> parallel HTTP requests for the same URL, effectively serializing them. |
| 46 | +</I> |
| 47 | +I do not think Squid does that by default. Either you are |
| 48 | +misinterpreting Squid code or you are looking at code related to |
| 49 | +collapsed_forwarding feature (see squid.conf.documented). That feature |
| 50 | +is off by default (and it queues but does not serialize parallel requests). |
| 51 | + |
| 52 | +I recommend providing at least one specific code example to |
| 53 | +illustrate/substantiate your claim. |
| 54 | + |
| 55 | + |
| 56 | +HTH, |
| 57 | + |
| 58 | +Alex. |
| 59 | + |
| 60 | + |
| 61 | +><i> I |
| 62 | +</I>><i> would like to understand the fundamental design rationale behind these |
| 63 | +</I>><i> restrictions. Specifically: Are these blocks in place due to specific |
| 64 | +</I>><i> architectural constraints (such as memory management or Store Entry |
| 65 | +</I>><i> state transitions)? Are there known side effects or risks I should be |
| 66 | +</I>><i> aware of if I attempt to implement parallel requesting for identical |
| 67 | +</I>><i> objects in a research environment? I want to ensure I fully understand |
| 68 | +</I>><i> the system's design philosophy before proceeding with any modifications. |
| 69 | +</I>><i> Thank you for your time and insights. |
| 70 | +</I> |
| 71 | +</PRE> |
| 72 | + |
| 73 | +<!--endarticle--> |
| 74 | + <HR> |
| 75 | + <P><UL> |
| 76 | + <!--threads--> |
| 77 | + <LI>Previous message (by thread): <A HREF="009977.html">[squid-dev] Architectural inquiry: Design rationale behind serialized request handling for identical URLs |
| 78 | +</A></li> |
| 79 | + |
| 80 | + <LI> <B>Messages sorted by:</B> |
| 81 | + <a href="date.html#9978">[ date ]</a> |
| 82 | + <a href="thread.html#9978">[ thread ]</a> |
| 83 | + <a href="subject.html#9978">[ subject ]</a> |
| 84 | + <a href="author.html#9978">[ author ]</a> |
| 85 | + </LI> |
| 86 | + </UL> |
| 87 | + |
| 88 | +<hr> |
| 89 | +<a href="https://lists.squid-cache.org/listinfo/squid-dev">More information about the squid-dev |
| 90 | +mailing list</a><br> |
| 91 | +</body></html> |
0 commit comments