|
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. |
|||
|
03:49
guifa left
04:21
Pe_Elle joined
04:26
Pe_Elle left
11:37
Pe_Elle joined
11:42
Pe_Elle left
12:30
guifa joined
|
|||
| librasteve | patrickb: great job! | 17:46 | |
| SmokeMachine: I guess I have failed to convince you that having a single Cro Component module that can accommodate both crotmp and functional styles will be sufficient benefit. Tbh this is a gut feeling and I have no evidence either way. Thanks for your patience - I will take your advice and go a parallel path. | 17:52 | ||
|
17:55
sena_kun joined
|
|||
| Two parting shots: (i) is accessible is imo a poor name for this trait since it is easily confused with general accessibility features and (ii) I have come to like the idea of :id(0) when I have just one singleton component - ie if you expressly set id=0 then the instance becomes the only instance in town (and I am a bit queasy about EVALs in the route block so can just use url-path = '.../0/...' | 17:55 | ||
|
18:54
sena_kun left
19:54
xinming joined
|
|||
| xinming | Hi, How do we ask cro to listen to all ipv4 and ipv6 interfaces in Cro::HTTP::Server ??? | 19:55 | |
| It seems, 0.0.0.0 listens to all ipv4 addresses, and :: listens to all ipv6 addresses, What is the right way to handle them both instead of starting 2 instances? | |||
|
21:31
Pe_Elle joined
21:36
Pe_Elle left
22:04
sena_kun joined
23:19
guifa left,
guifa joined
23:37
sena_kun left
|
|||