@niwinz: could you please elaborate what is the reason catacumba has such small heap footptint? Is it because ratpack doing something differently than others or catacumba or both? Just curious, didn't look at it very carefully yet
ratpack is a very lightweigh layer on top of netty
and netty is designed to be very small in fooprint
and high performant
and catacumba is also very lightweight and has some optimizations
I know about that but I was suprised that it works pretty well with very low memory resources
Many java applications can't use the aws micro instance bacause of memory, but for catacumba this is not a problem
Is httpurr.auth in 0.5.0 ?
I seem not to be able to require it
Docs say “latest” so not sure if that implies 0.5.0
is only on cljs
but I'm not clearly inderstand why
in any case it will be deleted surelly because it is pretty inconsistent ...
ah, ok.
Something awesome to have is helpers for encode query parameters
I was just adding headers manually but noticed auth
forget about auth, it is brokern and legacy code that will be deleted in next versions
ok
I recomend use 0.6.0-SNAPSHOT
because it includes a lot of fixes and consistency improvements in the available impls
Is that master?
or close to what’s in master
yes is master
cool
thanks for the quick replies
😉
I hope we will release a new version soon...
niwiz: thanks! I read docs on catacumba and approach looks very interesting. I'll definitely try it on some pet project.
One thing I love about Aleph is that it has instrumented thread pools and queues from the box. Any plans on something like this for catacumba? I see "Instrumentation: TODO" in the docs :simple_smile:
@jetmind: it is not documented but is already in the code
see examples section 😉
great!