|
Welcome the channel on the development of Cro, a set of libraries for building reactive distributed systems, lovingly crafted to take advantage of all the Raku Programming Language has to offer (cro.services). This channel is being logged for historical purposes. Set by lizmat on 24 May 2021. |
|||
|
00:23
Xliff left
05:30
tbrowder left,
jdv left,
jdv joined,
tbrowder joined
05:53
jnthn left,
leont left,
zostay left,
Altreus left,
kawaii_ left
05:54
kawaii_ joined,
jnthn joined
05:55
leont joined,
zostay joined
05:57
Altreus joined
11:06
sena_kun joined
13:36
Xliff joined
17:46
sena_kun left
17:47
sena_kun joined
|
|||
| Xliff | \o | 18:49 | |
| Hi. I have static classes that I use to implement Applications at the Cro::Route layer. Is there a mechanism to attach request/response specific data to the request object so that my static Application classes can remain thread (and request) safe. | 18:50 | ||
| The use case here is Database Pools. | 18:51 | ||
| Thanks. | |||
|
18:56
xinming left
18:59
xinming joined
19:09
Xliff left
|
|||
| jnthn | Xliff: Use the `annotations` hash on the Cro::HTTP::Request object: `$request.annotations<conn> = $conn` | 21:44 | |
| (It's how Log::Timeline attaches a task to a request so it can log its processing details) | 21:45 | ||
| (But was made a generic mechanism for use-cases like yours.) | |||
|
22:29
sena_kun left
22:31
sena_kun joined
22:55
sena_kun left
|
|||