|
Cro: libraries and tools for building reactive services in Perl 6 | cro.services/ | Logs: irclog.perlgeek.de/cro/ Set by moderator on 10 March 2018. |
|||
|
00:17
lizmat joined
02:05
FROGGS_ joined
02:58
ilbot3 joined
|
|||
| moderator | Cro: libraries and tools for building reactive services in Perl 6 | cro.services/ | Logs: irclog.perlgeek.de/cro/ | ||
|
03:24
stmuk_ joined
09:10
sena_kun joined
|
|||
| FROGGS | is there a way that cro serializes my response (a structure) according to the Accept request header? | 15:49 | |
|
15:52
stmuk_ joined
|
|||
| jnthn | Nothing so magical at the moment. There's a few ways one could set something like that up, however | 15:52 | |
| The most boring being to just take the accept header preference and pass it to content when setting the response | 15:53 | ||
| An alternative being to write an implementation of the Cro::BodySerializer role that grabs the request object via the response object, looks at the accept header, and does the right thing | 15:54 | ||
| FROGGS | just wrote a sub that does that, and now I probably wont use it :P | 16:16 | |
| (because I realised that there is no xml serializer by default) | 16:29 | ||
| this evening I might try to port my authorization code over from Mojolicious | 16:37 | ||
| timotimo | i wonder if stack growth from continuations only impacts the thread pool scheduler or if it also hits gather/take | 17:03 | |