01:04 <slfritchie> illotum: You can call the socket's getsockopt() & setsockopt() functions inside of your TCPConnectionNotify class's callback, e.g. in the fun ref connected(conn: TCPConnection ref) callback. The docs at https://stdlib.ponylang.org/net-TCPConnection/#getsockopt can help show the way, I hope. Holler if it still isn't clear.

01:07 <slfritchie> Most of the constants that might be useful for a UNIX'ish or Windows platform are defined in the OsSockOpt module: https://stdlib.ponylang.org/net-OSSockOpt/

01:09 <slfritchie> If the constant that you need isn't present in the OsSockOpt module, then you'll have to discover what it is (diving through /usr/include/* header files, for example) and then hard-code it into your Pony code.

10:51 <Candle> What pattern do people recommend to get a field out of lots of actors [of the same type] into a list?

11:54 <vaninwagen> Do you know how many actors there is and are you in control of their code? Or is it some 3rd party actor?

11:55 <vaninwagen> You could have another actor gather them in a list, create it with the expected number of values and then call a behaviour on the field actors that sends the field to the gathering actor

11:56 <vaninwagen> You could have a promise on the gathering actor that is set when all values arrived

11:56 <vaninwagen> Does that make sense?

12:04 <Candle> That makes sense, yes. There can be 1000s of actors, and it's code that I control.

12:07 <vaninwagen> Cool, one could even make this some generic thingy that will save people some boilerplate.

13:33 <Candle> Yes. A list of actors is the input, We know we have N actors in the input, so we know how many responses we should have, on the Nth response, call the callback with the resulting set.

13:34 <Candle> There are some error conditions there that make me want to add a timeout, but that's ugly.

14:08 <vaninwagen> I also thought a timeout does make sense

14:42 <Candle> I think that a timeout feature is after the "first make it work" phase!

16:56 <slfritchie> Candle: The Promises package may take care of your "what to do after getting N responses from N actors" task. https://stdlib.ponylang.org/promises--index ... Promise.join() is given an iterator of Promises and creates a new Promise. Using next() on that that new promise will give you the ability to inspect the concrete return values of the promises from the iterator.