Newest at the top
| 2026-01-23 11:49:11 +0100 | <bwe> | Then MVar is nothing but a (changeable) State across different threads, does that mean different binaries? How do they find them each other, then? |
| 2026-01-23 11:47:20 +0100 | <bwe> | ...and I thought data stored in Reader doesn't change (once loaded). |
| 2026-01-23 11:46:35 +0100 | fp | (~Thunderbi@2001:708:20:1406::10c5) fp |
| 2026-01-23 11:41:14 +0100 | hellwolf | (~user@e7d0-28a4-0ea3-c496-0f00-4d40-07d0-2001.sta.estpak.ee) hellwolf |
| 2026-01-23 11:40:33 +0100 | <danza> | but they should have one MVar per query? Anyway yes, sounds like something better solved in hyperbole |
| 2026-01-23 11:39:45 +0100 | Googulator | (~Googulato@team.broadbit.hu) (Ping timeout: 272 seconds) |
| 2026-01-23 11:39:00 +0100 | <[exa]> | bwe: yeah MVars are great for that, loading them doesn't cost anything and you can atomically flip to the new state |
| 2026-01-23 11:38:43 +0100 | <bwe> | danza: I am quite tolerant for outdated database states within a range of up to 3 minutes (update time of my internal cache). |
| 2026-01-23 11:37:16 +0100 | <bwe> | [exa]: Well, if I get you right, that is similar to what I thought. "How can I update some thing in a different thread from another (that just sleeps between updates)?" |
| 2026-01-23 11:36:34 +0100 | <[exa]> | (I'm not very sure how hyperbole works but if you use Reader, pushing in the MVar shouldn't be a big issue.) |
| 2026-01-23 11:35:59 +0100 | <bwe> | danza: So, the internal data cache actually lies in the hyperbole framework. But I pull it only in on start of warp. |
| 2026-01-23 11:35:58 +0100 | <[exa]> | bwe: you can have a MVar in the Reader that points to data, and replace it every now and then from a completely independent thread? |
| 2026-01-23 11:35:52 +0100 | Googulator23 | (~Googulato@team.broadbit.hu) |
| 2026-01-23 11:34:47 +0100 | <bwe> | [exa]: I currently load data when the web server starts. It hands over the data to hyperbole web framework in a Reader context through Effectful. What I want is that it loads it all 3 minutes for example without reloading the web server altogether. |
| 2026-01-23 11:30:59 +0100 | Square2 | (~Square@user/square) Square |
| 2026-01-23 11:30:55 +0100 | hellwolf | (~user@4cde-2438-8978-87b1-0f00-4d40-07d0-2001.sta.estpak.ee) (Ping timeout: 264 seconds) |
| 2026-01-23 11:28:10 +0100 | merijn | (~merijn@77.242.116.146) merijn |
| 2026-01-23 11:28:03 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) (Read error: Connection reset by peer) |
| 2026-01-23 11:25:39 +0100 | Googulator | (~Googulato@team.broadbit.hu) |
| 2026-01-23 11:17:09 +0100 | ljdarj | (~Thunderbi@user/ljdarj) ljdarj |
| 2026-01-23 11:14:32 +0100 | trickard | (~trickard@cpe-93-98-47-163.wireline.com.au) |
| 2026-01-23 11:14:20 +0100 | trickard | (~trickard@cpe-93-98-47-163.wireline.com.au) (Read error: Connection reset by peer) |
| 2026-01-23 11:13:49 +0100 | <danza> | data-based contents would be provided at application level, but it's tricky to cache because database contents can change |
| 2026-01-23 11:12:56 +0100 | vanishingideal | (~vanishing@user/vanishingideal) (Ping timeout: 240 seconds) |
| 2026-01-23 11:07:29 +0100 | <[exa]> | bwe: can you be more specific on "internal data cache"? (does wai have a cache?) |
| 2026-01-23 11:06:32 +0100 | __monty__ | (~toonn@user/toonn) toonn |
| 2026-01-23 11:05:50 +0100 | xff0x | (~xff0x@fsb6a9491c.tkyc517.ap.nuro.jp) (Ping timeout: 265 seconds) |
| 2026-01-23 11:05:10 +0100 | <danza> | are you sure that is the right level of abstraction? Wai/warp sound too close to the server for a cache that has to query a database |
| 2026-01-23 11:04:00 +0100 | fp | (~Thunderbi@2001-14ba-6e24-3000--198.rev.dnainternet.fi) (Ping timeout: 252 seconds) |
| 2026-01-23 10:50:47 +0100 | vanishingideal | (~vanishing@user/vanishingideal) vanishingideal |
| 2026-01-23 10:48:07 +0100 | Googulator | (~Googulato@team.broadbit.hu) (Quit: Client closed) |
| 2026-01-23 10:35:33 +0100 | XZDX | (~xzdx@user/XZDX) XZDX |
| 2026-01-23 10:35:33 +0100 | XZDX | (~xzdx@2601:404:ce00:b795:214:51ff:fe83:9855) (Changing host) |
| 2026-01-23 10:33:41 +0100 | XZDX | (~xzdx@2601:404:ce00:b795:214:51ff:fe83:9855) |
| 2026-01-23 10:33:37 +0100 | <bwe> | How can I let wai / warp update an internal data cache regularly by querying some database (no, I don’t mean response cache)? |
| 2026-01-23 10:32:29 +0100 | xff0x | (~xff0x@fsb6a9491c.tkyc517.ap.nuro.jp) |
| 2026-01-23 10:31:43 +0100 | housemate | (~housemate@202.7.248.67) (Remote host closed the connection) |
| 2026-01-23 10:31:38 +0100 | housemate | (~housemate@202.7.248.67) housemate |
| 2026-01-23 10:31:09 +0100 | housemate | (~housemate@202.7.248.67) (Remote host closed the connection) |
| 2026-01-23 10:30:41 +0100 | housemate | (~housemate@202.7.248.67) housemate |
| 2026-01-23 10:30:37 +0100 | xff0x | (~xff0x@fsb6a9491c.tkyc517.ap.nuro.jp) (Ping timeout: 264 seconds) |
| 2026-01-23 10:30:11 +0100 | housemate | (~housemate@202.7.248.67) (Max SendQ exceeded) |
| 2026-01-23 10:30:01 +0100 | CiaoSen | (~Jura@2a02:8071:64e1:da0:5a47:caff:fe78:33db) CiaoSen |
| 2026-01-23 10:29:30 +0100 | housemate | (~housemate@202.7.248.67) housemate |
| 2026-01-23 10:27:18 +0100 | skum | (~skum@user/skum) skum |
| 2026-01-23 10:27:17 +0100 | housemate | (~housemate@202.7.248.67) (Max SendQ exceeded) |
| 2026-01-23 10:26:58 +0100 | machinedgod | (~machinedg@d75-159-126-101.abhsia.telus.net) machinedgod |
| 2026-01-23 10:26:31 +0100 | housemate | (~housemate@202.7.248.67) housemate |
| 2026-01-23 10:25:38 +0100 | chele | (~chele@user/chele) chele |
| 2026-01-23 10:25:25 +0100 | Googulator | (~Googulato@team.broadbit.hu) |