There is a mistake in my first mail : the hook is "slow", but fast enought to handle a request
So when it start flooding, the first request will be processed in time, then another, slowly sliding into obsoletes requests Anyway thank you both for the insight, I have now a couple of lead to work on On 31/07/2017 17:18, Francis Dupont wrote: > Tomek Mrugalski writes: >> But as Francis said, this would be another trick. The ultimate solution >> would be to implement async hooks. > > => I am not sure they (async hooks) can save you: if the response depends > on a slow processing the client will timeout anyway. > Note if the problem is a long hook startup you should initiate it > when the hook is loaded (unfortunately today a hook is loaded more than > once?) > > Regards > > Francis Dupont <fdup...@isc.org> > _______________________________________________ > Kea-users mailing list > Kea-users@lists.isc.org > https://lists.isc.org/mailman/listinfo/kea-users > _______________________________________________ Kea-users mailing list Kea-users@lists.isc.org https://lists.isc.org/mailman/listinfo/kea-users
