synopse

As of late 2025, after an exhaustive search across GitHub, forums, documentation, and general web sources — no, there is still no other solution (open-source or proprietary) that comes anywhere close to what mORMot 2's THttpPeerCache does in the exact niche you're targeting:

• A transparent forward HTTP/HTTPS caching proxy
• With automatic UDP-multicast peer discovery (WS-Discovery style)
• Live streaming to concurrent requesters (one upstream connection → many local peers get the data in real time)
• Whole-object level but with the smart “one wins and feeds the others instantly” behavior you described
• Fully cross-platform native code (Windows + Linux + macOS out of the box, no WSL/Java/mono required)

Closest things that exist (and why they don’t match)

synopse

mORMot 2's MongoDB client (in mormot.db.nosql.mongodb.pas) currently supports only MONGODB-CR (deprecated) and SCRAM-SHA-1 for authentication in TMongoClient.Auth. It lacks native support for SCRAM-SHA-256, the default mechanism in MongoDB 4.0+ (and required for many modern deployments like Atlas clusters with stricter security).

Current Status

• The TMongoClient.Auth method checks an enumeration like TMongoAuthMechanism = (maCR, maSHA1) and implements the old MONGODB-CR nonce-based flow or the SCRAM-SHA-1 conversation.
• No maSHA256 option exists, and the SCRAM code uses SHA-1 digests (from SynCommons SHA-1 functions).
• mORMot 2's own internal authentication (e.g., for REST servers) supports full SCRAM (including SHA-256 variants and even PBKDF2/SHA3), but the MongoDB client layer has not been updated for SCRAM-SHA-256 yet.

What Needs to Be Done to Add SCRAM-SHA-256

To add it properly (cleanly, without breaking existing code):

synopse

c:\Temp\tempbuild\exe>mormot2tests

   mORMot2 Regression Tests
  --------------------------


1. Core units

 1.1. Core base:

synopse

Differences Between SCRAM-SHA-1 and SCRAM-SHA-256 in MongoDB

SCRAM (Salted Challenge Response Authentication Mechanism) is MongoDB's default authentication method, based on IETF RFC 5802 (for SHA-1) and RFC 7677 (for SHA-256). Both variants follow a similar challenge-response flow to avoid sending plaintext passwords over the wire, but they differ in security, hashing, and MongoDB-specific tweaks. SCRAM-SHA-256 became the default in MongoDB 4.0+ due to SHA-1's deprecation and known weaknesses (e.g., collision vulnerabilities).

Here's a comparison:

Aspect	SCRAM-SHA-1	SCRAM-SHA-256
Hashing Algorithm	SHA-1 (160-bit output)

synopse

No, you cannot connect to MongoDB using SCRAM-SHA-256 authentication for a user that was explicitly created with only the SCRAM-SHA-1 mechanism (i.e., specifying mechanisms: ["SCRAM-SHA-1"] in db.createUser()).

Here's why:

• When creating a user, the mechanisms field determines which SCRAM variants' credentials are stored for that user. SCRAM-SHA-1 and SCRAM-SHA-256 are distinct: the former uses SHA-1 hashing, while the latter uses SHA-256 and requires server-side password digestion (passwordDigestor: "server").
• If only SCRAM-SHA-1 is specified, the server stores only the corresponding salted password verifier for that mechanism. Attempting SCRAM-SHA-256 authentication will fail because the server lacks the SHA-256 credentials for the user.
• By default (without specifying mechanisms), MongoDB creates users with both SCRAM-SHA-1 and SCRAM-SHA-256 credentials, allowing clients to authenticate using either. You can also explicitly add both via mechanisms: ["SCRAM-SHA-1", "SCRAM-SHA-256"]

synopse

   mORMot2 Regression Tests
  --------------------------


1. Core units

 1.1. Core base:
  - Records: 893 assertions passed  641us
  - TSynList: 3,007 assertions passed  150us

synopse

  {
    "merchantSku": "NCL17674",
    "barcode": "20379360",
    "hbSku": "HBCV00009FDX66",
    "variantGroupId": "379292",
    "productName": "Kadın Lazer Kesim Dikişsiz Kadın Boxer Külot 3 lü Paket TEN",
    "productStatus": "Satışa Hazır",
    "taskDetails": [

    ],

synopse

   mORMot2 Regression Tests
  --------------------------


1. Core units

 1.1. Core base: 
  - Records: 893 assertions passed  82us
  - TSynList: 3,007 assertions passed  8us

synopse

   mORMot2 Regression Tests
  --------------------------


1. Core units

 1.1. Core base:
  - Records: 893 assertions passed  272us
  - TSynList: 3,007 assertions passed  70us

synopse

R0001: [001] EMR_HEADER	(s=108)	{{ Bounds(76,49,1257,1060), Frame(0,0,21404,27940), ver(0x10000), size(1061676), recs(2440), handles(42), pals(0), dev_pix(1920,931), dev_mil(320,240), pixf_size(0), pixf_ofs(0), openGL(0) }}
R0002: [070] EMR_GDICOMMENT	(s=519296)	{GDI.Embedded WMF}
R0003: [017] EMR_SETMAPMODE	(s=12)	{iMode(8=MM_ANISOTROPIC)}
R0004: [011] EMR_SETVIEWPORTEXTEX	(s=16)	{szlExtent(1284,1084)}
R0005: [009] EMR_SETWINDOWEXTEX	(s=16)	{szlExtent(1284,1084)}
R0006: [010] EMR_SETWINDOWORGEX	(s=16)	{ptlOrigin(-96,-96)}
R0007: [009] EMR_SETWINDOWEXTEX	(s=16)	{szlExtent(5056,6600)}
R0008: [033] EMR_SAVEDC	(s=8)
R0009: [021] EMR_SETSTRETCHBLTMODE	(s=12)	{iMode(3=COLORONCOLOR)}
R0010: [081] EMR_STRETCHDIBITS	(s=146184)	{rclBounds(957,49,1255,108), Dest[x:3673, y:204, cx:1175, cy:362)], dwRop(0x00CC0020), Src[x:0, y:0, cx:591, cy:245, iUsage:0, offBmi:80, Bmi:1064, offBits:1144, Bits:145040] BmiHeader[biSize:40, biWidth:591, biHeight:245, biPlanes:1, biBitCount:8, biCompression:0, biSizeImage:0, biXPelsPerMete