Dan Gudmundsson

So we agreed that this is useful information but it was decided that we should have an api for setting and getting this information, so that where (and how) the...

We have not discussed the name or where to put them it was just a suggestion, we leave that to you for now and will take that discussion when a...

Yes, I have been thinking on this on and off, and don't know what to do about it. What I want to avoid is a performance load on the target...

We decided to use a functional interface so we can change it later to something with more performance. But maybe move the functions to proc_lib and add a new function...

I think the wrong label was applied, sorry for taking some time, this is stuff that goes to the bottom of the priority list for us :-/ And I have...

Hidden nodes where not include for erl_interface nodes and so on, nodes that can't handle all rpc:call that are done to fetch data, so I don't think I like that....

> Could there be some check only for connected nodes if they support observer functionality and only list those that do? I don't know how to test that. > Do...

After (not) sleeping on this for a couple of nights, I I think I like your last suggestion :-)

So that didn't go well, the erts team didn't like this idea at all. They think we should work towards the correct way and add a capability on the erlang...

You will need to remove the enclosing [] in fresh_crl since get_crls have already removed the list. ``` fresh_crl(#'DistributionPoint'{distributionPoint = {fullName, Names}}, CRL) -> case get_crls(Names, undefined) of not_available ->...