[00:23] *** Xliff left
[05:30] *** tbrowder left
[05:30] *** jdv left
[05:30] *** jdv joined
[05:30] *** tbrowder joined
[05:53] *** jnthn left
[05:53] *** leont left
[05:53] *** zostay left
[05:53] *** Altreus left
[05:53] *** kawaii_ left
[05:54] *** kawaii_ joined
[05:54] *** jnthn joined
[05:55] *** leont joined
[05:55] *** 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
[18:49] <Xliff> \o

[18:50] <Xliff> 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:51] <Xliff> The use case here is Database Pools.

[18:51] <Xliff> Thanks.

[18:56] *** xinming left
[18:59] *** xinming joined
[19:09] *** Xliff left
[21:44] <jnthn> Xliff: Use the `annotations` hash on the Cro::HTTP::Request object: `$request.annotations<conn> = $conn`

[21:45] <jnthn> (It's how Log::Timeline attaches a task to a request so it can log its processing details)

[21:45] <jnthn> (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